docs(merge-queue): document stack support#11235
Merged
mergify[bot] merged 1 commit intomainfrom Apr 23, 2026
Merged
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
Add a dedicated `/merge-queue/stacks` page describing how the Merge Queue handles stacks created by `mergify stack push`. The integration was previously undocumented despite covering several engine features: - Stack detection (head/base chain plus `Depends-On:` markers) - Auto-propagation of `@mergifyio queue` from the top PR to every predecessor - Stack-aware base resolution (every stacked PR is queued against the stack root, not its parent branch) - Stack-aware batching guarantees: same scope group, bottom-up order - Cascade dequeue (`StackPredecessorDequeued`) when a predecessor fails - Limits: max stack depth of 20, drafts block propagation Also adds a "Stacked PRs" sidebar entry under Merge Queue, and cross-links the new page from the places users already look for stack and merge-queue information: - Merge Queue index: rows for "Stacked PRs" in both the problem-to-feature and key-features tables - /stacks/team: replace the generic blurb with single-comment stack queueing - /stacks/reviewing: rewrite the merge tip with the actual @Mergifyio queue workflow - /stacks/concepts: explain that the Depends-On marker is also the signal the queue uses for stack detection Change-Id: I1fc66332f5f474a5b6a0cbd89362c9c8c20dbec0
jd
force-pushed
the
devs/jd/worktree-docs-queue-stack/document-stack-support--1fc66332
branch
from
d01d1ff to
67ff744
Compare
Member
Author
Revision history
|
There was a problem hiding this comment.
Pull request overview
Adds missing documentation for how Merge Queue behaves with stacked PRs created by mergify stack push, and exposes it in the Merge Queue sidebar navigation.
Changes:
- Add a new “Stacked Pull Requests” documentation page under Merge Queue (
/merge-queue/stacks). - Add a “Stacked PRs” entry in the Merge Queue sidebar so the page is discoverable.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/content/navItems.tsx | Adds sidebar navigation entry for the new Merge Queue stacks page. |
| src/content/docs/merge-queue/stacks.mdx | New doc page describing stack detection, propagation, batching behavior, cascade dequeue, and limits. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sileht
approved these changes
Apr 23, 2026
remyduthu
approved these changes
Apr 23, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 32 seconds in the queue, including 2 minutes 11 seconds running CI. Required conditions to merge
|
51 tasks
mergify
Bot
deleted the
devs/jd/worktree-docs-queue-stack/document-stack-support--1fc66332
branch
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.
Add a dedicated
/merge-queue/stackspage describing how the MergeQueue handles stacks created by
mergify stack push. The integrationwas previously undocumented despite covering several engine features:
Depends-On:markers)@mergifyio queuefrom the top PR to everypredecessor
stack root, not its parent branch)
StackPredecessorDequeued) when a predecessor failsAlso adds a "Stacked PRs" sidebar entry under Merge Queue, and
cross-links the new page from the places users already look for stack
and merge-queue information:
problem-to-feature and key-features tables
queueing
@Mergifyio queue workflow
signal the queue uses for stack detection