ci(mutation): drop pull_request trigger, weekly schedule only#17
ci(mutation): drop pull_request trigger, weekly schedule only#17williaby wants to merge 1 commit into
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 on otherwise-mergeable PRs. 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 Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ 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 |
|
There was a problem hiding this comment.
Pull request overview
Updates the repository’s mutation testing workflow to run only on a weekly schedule (plus manual dispatch) so mutation testing remains available for drift/regression detection without adding PR latency/timeouts.
Changes:
- Removed the
pull_requesttrigger and PR-commenting behavior from the mutation testing workflow. - Updated concurrency grouping to be branch-based (no PR-number component).
- Normalized
fail-under-thresholdto be opt-in only forworkflow_dispatch.
| fail_under_threshold: | ||
| description: 'Fail the run if score is below threshold (default: false)' | ||
| required: false | ||
| default: 'false' | ||
| type: string |
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