[Fix] Mutation warnings appear twice after drafts become ready - #1645
zoomote[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: Mark the PR ready. Required CI must pass before CodeRabbit starts. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What changed
Changed-code mutation testing now skips pull-request jobs while the PR is a draft. It starts when the PR becomes ready and continues to run for reviewable opens, new commits, reopens, and merge-queue checks.
Focused workflow tests model the draft-open to ready transition and preserve the supported reviewable event paths.
Why this change was made
PR #1644 showed GitHub retaining annotations from both the draft-open run and the ready-for-review run for the same head SHA. Within-run warning deduplication cannot remove annotations belonging to an earlier workflow run.
Impact
Draft PR creation no longer emits mutation annotations that GitHub can display again beside the ready-for-review results. Mutation enforcement remains unchanged once a PR is reviewable and in the merge queue.