fix(ci): wire required checks for the merge queue#105
Conversation
Adds a `merge_group` trigger to the four required-check workflows so each required context reports inside the merge queue. NOTE: this template seeds new repos; fixing it prevents future repos from inheriting the stall. Part of the org-wide merge-queue stall remediation. A required merge queue stalls when required-check workflows do not trigger on the merge_group event; the queue dispatches merge_group, waits for checks that never report, and times out. See reference-library PR #64 for the reference fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 28 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
1 participant
Summary
Adds a
merge_grouptrigger to the four required-check workflows so each required context reports inside the merge queue. NOTE: this template seeds new repos; fixing it prevents future repos from inheriting the stall.Files changed
.github/workflows/ci.yml.github/workflows/pr-validation.yml.github/workflows/reuse.yml.github/workflows/security-analysis.ymlWhy
GitHub merge queues dispatch a
merge_groupevent, notpull_request. Arequired status check whose workflow does not trigger on
merge_groupneverreports on the queued commit, so the entry waits the full timeout and fails.
Required checks produced by reusable workflows surface as
caller-job / callee-job, which cannot match a bare ruleset context; the org pattern is anin-line aggregator job named exactly the bare context.
Landing this PR (deadlock)
For
merge_groupevents GitHub uses the workflow definition from the defaultbranch, so this fix does not take effect in the queue until it is on
main.This repo's merge-queue ruleset has no bypass actor, so an admin must break the
deadlock once: temporarily set the
merge-queueruleset to Evaluate (orDisabled), squash-merge this PR, then re-enable. Subsequent PRs drain normally.
Validation
actionlintandyamllint(repo config) pass on the changed files; no newfindings introduced. Generated as part of an org-wide read-only audit.