Repository navigation
ci: run the required checks on merge groups - #706
Conversation
Prepares the merge queue that replaces recheck-open-prs (#704): the queue waits for CI - Required Checks on each group, so CI must start on merge_group before the ruleset is active. The version bump gate diffs against the group's base. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Why
#704 replaces
recheck-open-prswith a merge queue. The queue waits forCI - Required Checkson every merge group, so CI must start onmerge_groupbefore the queue ruleset is turned on. Otherwise queued PRs wait for a check that never starts.What
ci.yamlalso runs onmerge_group. Group refs are unique, so the existing ref-keyed concurrency never cancels one group for another.merge_group.base_shain a group, so it checks exactly what the group adds to main.Order
deploy/repository-rulesets/require-merge-queue-on-agent-plugins.yaml).recheck-open-prsonce the queue is live. That one closes Replace recheck-open-prs with a merge queue #704.Validation
actionlintclean.ci-script-test-sharding-workflow,ci-skill-validation-workflow,guard-bundled-skill-editsandprepare-merged-marketplace-releaseself-tests pass.Part of #704.
🤖 Generated with Claude Code