docs(stacks): cross-link to merge queue stack documentation#11236
Closed
Conversation
Add a dedicated 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" entry under Merge Queue in the sidebar so the page is reachable from the navigation tree. Change-Id: I1fc66332f5f474a5b6a0cbd89362c9c8c20dbec0
Surface the new `/merge-queue/stacks` page from the places users already look for stack and merge-queue information: - Merge Queue index: add rows for "Stacked PRs" in both the problem-to-feature and key-features tables - `/stacks/team`: replace the generic "complements well" blurb with a concrete description of single-comment stack queueing - `/stacks/reviewing`: rewrite the merge tip with the actual `@mergifyio queue` workflow - `/stacks/concepts`: explain that the `Depends-On:` marker isn't only for humans — it's the signal the queue uses for stack detection Change-Id: I433bc3a8faf2920d756f753a9c2243d02e3f9e5d
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. 🔴 ⛓️ Depends-On RequirementsWaiting for:
This rule is failing.Requirement based on the presence of
🔴 👀 Review RequirementsWaiting for:
This rule is failing.
🔴 🔎 ReviewsWaiting for:
This rule is failing.
🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
d01d1ff to
67ff744
Compare
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.
Surface the new
/merge-queue/stackspage from the places usersalready look for stack and merge-queue information:
problem-to-feature and key-features tables
/stacks/team: replace the generic "complements well" blurb witha concrete description of single-comment stack queueing
/stacks/reviewing: rewrite the merge tip with the actual@mergifyio queueworkflow/stacks/concepts: explain that theDepends-On:marker isn'tonly for humans — it's the signal the queue uses for stack
detection
Depends-On: #11235