ci(mutation): drop pull_request trigger, weekly schedule only#41
Conversation
Mutation testing is wall-clock expensive (60-minute typical timeout per run). Wiring it as a PR check inflates merge latency and gates merges on flaky long-running signal that the weekly cron already covers. The previous fail-under-threshold expression also silently blocked merges. Changes: - Remove pull_request: trigger and concurrency PR-scope - Remove pull-requests: write permission (no longer posts PR comments) - Normalize fail-under-threshold to opt-in via workflow_dispatch input - Add fail_under_threshold workflow_dispatch input (default false) - Update header to document the policy and reference CI-053 Enforced fleet-wide by manifest check CI-053. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 26 minutes and 37 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Pull request overview
Adjusts the repository’s mutation testing GitHub Actions workflow to run only on a weekly schedule (plus manual dispatch), avoiding expensive per-PR mutation runs while still providing drift/regression visibility.
Changes:
- Removed the
pull_requesttrigger and PR-commenting behavior to avoid gating PRs with a typically long-running job. - Added a
workflow_dispatchinput to optionally fail the run when the mutation score is under the threshold. - Simplified concurrency grouping to be branch-based (since PR context no longer applies).
| default: 'false' | ||
| type: string |
|
Re-resolve against current main (#36/#41/#37 landed after the first sync): - mutation-testing.yml, scorecard.yml: take main's versions (preserve the already-merged #41/#36 changes; #40's per-job permission tightening on those two files is dropped to avoid reverting merged work). - CHANGELOG.md: keep both the Security (this PR) and Documentation (main) sections. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Removes the
pull_request:trigger and normalizes the fail-under-threshold expression, enforcing manifest check CI-053. Mutation testing is wall-clock expensive (60-minute typical timeout); weekly drift detection covers the regression-spotting need without gating PR merges.Generated with Claude Code