Ignore if coverage report fails #209
Merged
+1
−0
Conversation
This file contains 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
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
|
That's quite an interesting limitation, actually. I think this action will only work from a pull request event and can't be manually dispatched. So how would you see the coverage of an external contribution? It's a bit surprising that it wouldn't work as the external user does have permission to comment on this repo. Would their GITHUB_TOKEN not? |
|
The coverage report will be in the test report, just can't be posted to the PR without tokens it seems. |
|
I see! That seems tolerable. |
ajjackson
approved these changes
Feb 12, 2025
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.
Forked repos don't necessarily have the tokens for bot.
Ignore failures on coverage reporting as not essential.