feat(docs): document Merge Queue support for GitHub-native stacks - #12361
Conversation
|
This pull request is part of a Mergify stack:
|
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
Pull request overview
Updates the Merge Queue “Stacked Pull Requests” documentation to cover both Mergify Stacks and GitHub-native stacked PRs (gh-stack), clarifying detection, queueing behavior, and landing order.
Changes:
- Reframes the page intro to distinguish Mergify Stacks vs GitHub-native stacks and scopes the existing sections to Mergify Stacks.
- Adds a new GitHub-native section explaining per-member queueing, bottom-up landing, and GitHub restacking behavior.
- Documents the GitHub ruleset requirement for the
exemptbypass mode when merging GitHub-native stacks.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
e02a01c to
437c891
Compare
Revision history
|
437c891 to
a21059a
Compare
a21059a to
f18f2f3
Compare
c8cec50 to
0714c93
Compare
f18f2f3 to
e3514e5
Compare
0714c93 to
7f215a4
Compare
7f215a4 to
83b0f8d
Compare
e3514e5 to
66f9391
Compare
66f9391 to
ba7ae9b
Compare
83b0f8d to
f0af7cd
Compare
f0af7cd to
fd6c677
Compare
ba7ae9b to
b6d5b4a
Compare
|
@kozlek this pull request is now in conflict 😩 |
The queue merges GitHub's own stacked pull requests, and the page said nothing about them: it described Mergify Stacks throughout and stated that a stack is recognized only when each pull request carries a `Depends-On:` marker, which is not how GitHub-native stacks are detected. Lead the page with GitHub-native stacks: which members to queue, that they land one at a time from the bottom up, and the `exempt` bypass mode they need. Group the existing sections under a Mergify Stacks heading so their scope is explicit. Deep-link the ruleset page's incompatibility note to the new section. Part of MRGFY-8578 Change-Id: I81d627f9bf5c51c7bf60355625ae4209c5f0d3bd
b6d5b4a to
a7295f1
Compare
Merge Queue Status
This pull request spent 2 minutes 52 seconds in the queue, including 2 minutes 15 seconds running CI. Required conditions to merge
|
The queue merges GitHub's own stacked pull requests, and the page said
nothing about them: it described Mergify Stacks throughout and stated that a
stack is recognized only when each pull request carries a
Depends-On:marker, which is not how GitHub-native stacks are detected.
Lead the page with GitHub-native stacks: which members to queue, that they
land one at a time from the bottom up, and the
exemptbypass mode theyneed. Group the existing sections under a Mergify Stacks heading so their
scope is explicit.
Deep-link the ruleset page's incompatibility note to the new section.
Part of MRGFY-8578