Skip to content

Add Coverage Diff on PRs to GitHub CI#84

Draft
ye-spencer wants to merge 28 commits intospacetelescope:mainfrom
ye-spencer:add_cov_branch_diff
Draft

Add Coverage Diff on PRs to GitHub CI#84
ye-spencer wants to merge 28 commits intospacetelescope:mainfrom
ye-spencer:add_cov_branch_diff

Conversation

@ye-spencer
Copy link
Copy Markdown
Contributor

@ye-spencer ye-spencer commented Mar 30, 2026

Goal:

  • Create indicator of decreased coverage from main in PR (most likely a comment on the PR, not an outright CI failure)
  • Create a comment showing changes in coverage from main; only for files that actually changed in coverage
  • Have an indicator of coverage decrease
  • There should be configurable parameters such as level-of-total-coverage-to-fail-under (default 0), fail-under-this-much-decrease (default 100)
  • Add a command that can be ran in a specific environment to view per-line coverage

@ye-spencer ye-spencer force-pushed the add_cov_branch_diff branch from 4e245c2 to 8d47e62 Compare April 3, 2026 17:12
@ye-spencer ye-spencer force-pushed the add_cov_branch_diff branch from 72605d4 to 9b26e90 Compare April 30, 2026 19:56
@ye-spencer
Copy link
Copy Markdown
Contributor Author

One note is that the comments are NOT sticky; there will be one comment per run, which may get annoying. An initial look into how to do to sticky comments looked like a lot of work, but it can be a next step.

@ye-spencer
Copy link
Copy Markdown
Contributor Author

Also, it seems the CI will not run on this PR because it is from a fork. See actions in: ye-spencer#9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant