Repository navigation
fix(ci): Mergify auto-enqueue rule (queue_conditions alone are eligibility-only) - #7179
Conversation
… (queue_conditions alone are eligibility-only)
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
left a comment
There was a problem hiding this comment.
Code Review
This pull request updates the Mergify configuration in .mergify.yml to add an automatic enqueue rule. This rule triggers when the 'queue' label is applied to non-draft, conflict-free pull requests targeting release branches, automatically adding them to the release queue. No review comments were provided, and there is no additional feedback.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
commented
Jul 14, 2026
CI Coverage Report
Coverage artifact was not available for this run. PR Test PolicyThis PR changes production code in |
Live finding from the first queue probe (PR #7175, all checks green +
queuelabel): the Mergify check reported "can be added to the merge queue — use @Mergifyio queue" and never enqueued. In current Mergify semantics,queue_conditionsdefine eligibility only; auto-enqueue needs an explicitpull_request_rulesentry withactions: queue. This adds that trigger rule, mirroring the same conditions (owner-appliedqueuelabel onrelease/v*, non-draft, no conflict).Config-only file (nothing in build/tests/runtime reads it); same flow as #7168.