ci: treat 95% or higher project coverage as passing - #513
Conversation
Sorry, something went wrong.
The project coverage status had no configuration, so Codecov applied its default of allowing no decrease at all. Any pull request that added well-tested code still nudged the overall percentage down a fraction and failed the check. Set an explicit 95% target for project coverage. Coverage of the lines a pull request changes keeps its default behaviour, so new code is still expected to be tested.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sorry, something went wrong.
|
Warning Review limit reached@shenxianpeng, you've reached your PR review limit, so we couldn't start this review. Next review available in: 27 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR. To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 1cdf09c3-0bd7-4c60-adc0-3a5a30b8f3e3 📥 CommitsReviewing files that changed from the base of the PR and between 4922fec and 9befc26. 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
Keeps the repository root tidy, matching where dependabot and the other repository configuration already live. Codecov reads its configuration from the repository root, .github, or dev, so this location is equivalent.
|
Sorry, something went wrong.
Problem
The repository has no codecov.yml, so the project coverage status falls back to Codecov's default target of auto with a 0% threshold — meaning any decrease fails the check.
In practice this fails pull requests that are well tested. For example, in #512 Codecov reported:
…while codecov/project still failed at 97.43% (-0.11%), purely because adding 32 well-covered lines shifted the overall percentage by a fraction of a point.
Change
Add a codecov.yml that sets an explicit 95% target for project coverage. The project sits comfortably above that (currently ~97.4%), so the status now answers "is this project well covered?" rather than "did the percentage move at all?".
Coverage of the lines a pull request changes (codecov/patch) keeps Codecov's default behaviour, so new code is still expected to be tested.
Effect on open pull requests
Once this is on main, re-running CI on an open pull request will pick up the new configuration.
Generated by Claude Code