Uh oh!
There was an error while loading. Please reload this page.
chore(ci): add codecov config to reduce noise on small refactors - #1044
Merged
Conversation
alexanderankin
approved these changes
Jun 6, 2026
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
The repo currently has no
codecov.yml, so Codecov uses its strict defaults: any coverage drop (project) and any patch under 100% are reported as failing statuses on PRs.This produces frequent red checks on small refactors even when coverage is unchanged or trivially impacted (e.g. #1035, #1038).
This change adds a minimal
codecov.ymlthat keeps useful signal while removing the noise:coverage.status.project.default.threshold: 1%— allow up to a 1% project-coverage drop without failing.coverage.status.project.default.if_ci_failed: success— don't double-report when the CI run itself failed.coverage.status.patch.default.informational: true— still report patch coverage, but never block PRs on it.comment.require_changes: true— only post a PR comment when coverage actually changes.Validated with
curl --data-binary @codecov.yml https://codecov.io/validate→Valid!.Real coverage regressions will still surface (anything > 1% project drop), and contributors keep getting patch-coverage feedback — it just won't block.