Add GitHub native code coverage reporting#671
Conversation
…erage Co-authored-by: nikosavola <7860886+nikosavola@users.noreply.github.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideAdds GitHub-native code coverage reporting for pytest runs by extending coverage generation to all ubuntu-latest matrix entries and uploading coverage.xml via actions/upload-code-coverage, with appropriate permissions and checkout ref adjustments so coverage maps correctly to PR diffs while preserving existing main-branch coverage artifacts and badges. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Code Coverage OverviewLanguages: Python Python / code-coverage/pytestThe overall coverage in the branch is 90%. Coverage data for the branch is not yet available. Show a code coverage summary of the most covered files.
Updated |
|
@copilot Please fix the pre-commit hooks for this PR |
…nlint config, fix version comments Co-authored-by: nikosavola <7860886+nikosavola@users.noreply.github.com>
Head branch was pushed to by a user without write access
Fixed in 2nd commit. The issues were:
All pre-commit hooks now pass cleanly. |
Set up code coverage uploads to GitHub's Code Quality API via
actions/upload-code-coverage@v1, so coverage results appear directly on pull requests.Changes
--covflags now run on allubuntu-latestmatrix entries (not justmainpushes), giving GitHub both a baseline and per-PR comparisonactions/upload-code-coverage@v1step (pinned to82c7aee) uploadingcoverage.xmlascode-coverage/pytestwith languagePythoncode-quality: writepermission totest-codejobref: ${{ github.event.pull_request.head.sha || github.sha }}) so coverage line numbers map correctly to diffsExisting coverage badge generation and HTML artifact upload for
mainare unchanged.Summary by Sourcery
Enable uploading Python test coverage reports to GitHub’s Code Quality API from CI.
CI: