Repository navigation
Rulesets: merge queue in a repository ruleset; urgent changes - #6
Merged
Merged
Conversation
GitHub's organization rulesets reject a merge_queue rule (422 on create; the REST request schema lists no merge_queue type), so applying ci-merge-queue failed. The organization ruleset keeps the required ci-gate check and the ci-conformance workflow, and a `merge-queue` repository ruleset carries the queue. apply_rulesets.py puts it on every repository whose ci-tier is merge-queue; rulesets/ splits into org/ and repo/. CI.md: the two rulesets and the opt-in step, and a section on urgent changes: jump the queue; bypass only in an incident where CI itself is broken, logged as a deviation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
merge_queuerule: creatingci-merge-queuefailed with a 422, and the REST request schema lists no such type. The organization ruleset keeps the requiredci-gatecheck and theci-conformanceworkflow; a newmerge-queuerepository ruleset carries the queue, andapply_rulesets.pyputs it on every repository whoseci-tierismerge-queue.Test plan
self-test.yml.apply_rulesets.py --checkagainst the organization: property up to date, organization ruleset missing, no repository opted in.required_status_checksandworkflowsbut notmerge_queue.🤖 Generated with Claude Code