Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set a 1% theshold for coverage changes #1220

Merged
merged 1 commit into from
May 15, 2024
Merged

Conversation

haarg
Copy link
Member

@haarg haarg commented May 15, 2024

Our tests are somewhat inconsistent in their coverage, so coverage can go down slightly even with unrelated changes. We also have untested code, and small tweaks will often be shown as a reduction in coverage.

Setting a 1% threshold will reduce friction on both of these cases. Any larger changes will still require an increase in coverage, so we should still trend upward over time.

Our tests are somewhat inconsistent in their coverage, so coverage can
go down slightly even with unrelated changes. We also have untested
code, and small tweaks will often be shown as a reduction in coverage.

Setting a 1% threshold will reduce friction on both of these cases. Any
larger changes will still require an increase in coverage, so we should
still trend upward over time.
@oalders oalders merged commit 00bc1ad into master May 15, 2024
4 checks passed
@oalders oalders deleted the haarg/coverage-threshold branch May 15, 2024 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants