Coverage: Implement fail_under #654
Merged
+18
−7
Conversation
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
Daraan
force-pushed
the
coverage/fail-under
branch
from
5feaaa0 to
5232220
Compare
Contributor
Author
|
Works like expected. I just realized that coverage Therefore I adjusted the threshold by -1 to 95%. |
JelleZijlstra
approved these changes
Aug 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Set the fail threshold to 96% and implemented it by
fail_underin pyproject.toml.The fail will now be raised by
coverage reportand not the action. I set up the action to always run even if coverage report fails (still need to test first if it works as intended).