Repository navigation
ci(check): run on merge_group so the merge queue can gate PRs - #10
Merged
Merged
Conversation
The merge queue builds each PR as a temporary gh-readonly-queue/ candidate and fires a merge_group event; the required `check` status must run on that candidate or queued PRs never merge. Add the merge_group trigger. The `changes` gate treats merge_group as an unknown base and runs the full check, which is what we want in the queue. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alexkroman
enabled auto-merge
July 1, 2026 17:43
alexkroman
added this pull request to the merge queue
Jul 1, 2026
alexkroman
removed this pull request from the merge queue due to the queue being cleared
Jul 1, 2026
alexkroman
added this pull request to the merge queue
Jul 1, 2026
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
2 participants
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.
Adds a
merge_group:trigger tocheck.yml— required for the merge queue that was just enabled onmain.The merge queue builds each queued PR as a temporary
gh-readonly-queue/…candidate and fires amerge_groupevent. The requiredcheckstatus must run on that candidate, or queued PRs sit until they time out. Without this trigger the queue is non-functional.The
changesgate seesmerge_groupas an unknown base and runs the full check (exactly what we want in the queue — no docs-only skip inside the queue). actionlint passes.The merge queue is already active, so this PR (and #8/#9) will route through it — but the queue can't pass them until this trigger is on
main(chicken-and-egg). To land it, either:merge-queue-mainruleset enforcement to evaluate, merge this PR (and the others) normally, then flip back to active; orI can flip the ruleset to evaluate/back if you'd like.
🤖 Generated with Claude Code