Conversation
Pull Request Test Coverage Report for Build 1168927755
💛 - Coveralls |
Contributor
Author
|
the failed checks are that i cancelled the CI job for the push since there was no actual code change (although I kept it for the PR anyway) |
AlexanderSaydakov
approved these changes
Aug 26, 2021
Contributor
AlexanderSaydakov
left a comment
There was a problem hiding this comment.
Let's give this a go
Contributor
Author
|
Yay! It worked! If you go to the Github Actions tab and select this workflow, there's now an option to run it manually. |
Pull Request Test Coverage Report for Build 1168927755Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not highly confident, but I think the manual trigger part might not work until the workflow in the main branch specifies that option. Since this seems pretty low risk to merge, I'm proposing we try it.