ci(coverage): adding mandatory 80% level of coverage for diff (#239)#288
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #288 +/- ##
==========================================
+ Coverage 77.60% 79.65% +2.04%
==========================================
Files 57 57
Lines 2541 2541
==========================================
+ Hits 1972 2024 +52
+ Misses 569 517 -52 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
guzmud
changed the title
There was a problem hiding this comment.
Pull request overview
This PR introduces Codecov configuration and CI workflow updates to enforce a minimum coverage threshold on new/changed code, publish test results, and document the project’s quality gates for contributors.
Changes:
- Add
codecov.ymlto enforce a patch (diff) coverage target of 80%. - Update the coverage GitHub Actions workflow to generate
junit.xmland upload test results to Codecov. - Document CI quality checks and add
junit.xmlto.gitignore.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| CONTRIBUTING.md | Documents CI code-quality and coverage expectations for contributors. |
| codecov.yml | Configures Codecov status checks (project informational, patch target 80%). |
| .gitignore | Ignores generated junit.xml. |
| .github/workflows/coverage.yml | Generates JUnit XML output and uploads coverage/test results to Codecov. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
guzmud
force-pushed
the
ci/239-minimum-coverage-for-new-code
branch
2 times, most recently
from
8c6135a to
35a9778
Compare
jabesq
approved these changes
Jun 16, 2026
|
|
||
| - name: Print coverage summary | ||
| run: uv run coverage report -m --fail-under=70 | ||
| run: uv run coverage report -m --fail-under=80 |
Member
There was a problem hiding this comment.
suggestion: If you want to enforce this score, it would be better to set fail-under setting inside pyproject.toml
| with: | ||
| token: ${{ secrets.CODECOV_TOKEN }} | ||
| flags: connectors | ||
| flags: pyoaev |
Member
There was a problem hiding this comment.
suggestion: This flags is not needed because everything is pyoaev in this repos
guzmud
force-pushed
the
ci/239-minimum-coverage-for-new-code
branch
from
35a9778 to
860cd84
Compare
guzmud
force-pushed
the
ci/239-minimum-coverage-for-new-code
branch
from
860cd84 to
8cd881f
Compare
guzmud
force-pushed
the
ci/239-minimum-coverage-for-new-code
branch
from
8cd881f to
1a66a95
Compare
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 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.
Proposed changes
junit.xmlCONTRIBUTING.mdTesting Instructions
Related issues
Checklist