feat: add coverage delta reporting for PRs#16
Merged
Conversation
dims
force-pushed
the
coverage-delta-reporting
branch
from
9547723 to
ed3fa16
Compare
There was a problem hiding this comment.
Pull request overview
Adds PR coverage “delta” reporting by persisting a baseline coverage profile from the last successful main run and generating per-file coverage change details in the PR coverage comment.
Changes:
- Upload
coverage.outas a long-lived artifact to use as themainbaseline for later PR comparisons. - Enhance the
workflow_runcomment workflow to download PR + baseline coverage, detect changed Go files, and generate a delta report viafgrosse/go-coverage-report. - Extend the PR coverage comment body to include the delta report (or a fallback message when unavailable).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| .github/workflows/on-push-comment.yaml | Downloads PR + baseline coverage artifacts, computes changed-file list, optionally generates a delta report, and appends it to the PR comment. |
| .github/actions/go-coverage/action.yml | Uploads the raw coverage.out profile as an artifact so a later workflow can compare PR coverage vs. baseline. |
Enhance PR coverage comments to show what changed: - Upload coverage.out as artifact for baseline comparison - Download baseline from last successful main run - Use fgrosse/go-coverage-report to generate delta report - Show per-file coverage changes in PR comments Inspired by nvsentinel's consolidated-coverage-report pattern. Co-Authored-By: Claude Opus 4.5 <[email protected]> Signed-off-by: Davanum Srinivas <[email protected]>
dims
force-pushed
the
coverage-delta-reporting
branch
from
ed3fa16 to
ad6b4a6
Compare
Contributor
Coverage Report ✅
Coverage Badge |
Contributor
|
This pull request has been automatically locked since it has been closed for 90 days with no further activity. Please open a new pull request for related changes. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Add coverage delta reporting to PR comments, showing per-file coverage changes compared to the main branch baseline.
Motivation / Context
Adopted from nvsentinel's consolidated-coverage-report pattern. Makes it easier to see how a PR affects test coverage without manually comparing numbers.
Type of Change
Component(s) Affected
.github/actions/go-coverage,.github/workflows/on-push-comment.yamlImplementation Notes
coverage.outas artifact (90-day retention) for baseline comparisontj-actions/changed-filesto detect changed Go files (same as nvsentinel)fgrosse/go-coverage-reportto generate delta report (same as nvsentinel)Risk Assessment
🤖 Generated with Claude Code