ci: trigger on merge_group so a merge queue can be enabled#726
Merged
wbarnha merged 1 commit intoJul 21, 2026
Merged
Conversation
A GitHub merge queue validates each candidate as a `merge_group` event. The workflow only triggered on push / pull_request / release, so the required `check` job would never run for queued PRs and the queue would stall. Add the `merge_group` trigger so `master` is ready for a merge queue once a maintainer enables it in the repository rules. No behaviour change for normal pushes/PRs; the advisory jobs (integration, pypy) stay out of the required `check` gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HHPL4VFWQRQPpjR1gXSKyL
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.
Description
Makes
mastermerge-queue-ready. A GitHub merge queue validates each candidate as amerge_groupevent, but the workflow only triggered onpush/pull_request/release— so the requiredcheckjob would never run for a queued PR and the queue would stall indefinitely. This adds themerge_grouptrigger:checkjob (needs: [lint, test-pytest],alls-green) is already the single aggregated required status a queue wants, and now runs onmerge_grouptoo.test-integration,test-pypy,test-redis-integration) staycontinue-on-error/ out of thecheckgate, so they won't block the queue.To actually turn the queue on (maintainer, repo settings — not doable from a PR)
Settings → Rules / Rulesets (or branch protection on
master) → enable "Require merge queue" targetingmaster, with the required status check set to ✅ Ensure the required checks passing (thecheckjob). Pick merge method / max batch size as desired. This PR is the prerequisite; the toggle itself is admin-only.Top of the stacked chain (based on #725). YAML validated.
🤖 Generated with Claude Code
Generated by Claude Code