Skip to content

docs(stacks): cross-link to merge queue stack documentation#11236

Closed
jd wants to merge 2 commits intodevs/jd/worktree-docs-queue-stack/document-stack-support--1fc66332from
devs/jd/worktree-docs-queue-stack/cross-link-merge-queue-stack-docs--433bc3a8
Closed

docs(stacks): cross-link to merge queue stack documentation#11236
jd wants to merge 2 commits intodevs/jd/worktree-docs-queue-stack/document-stack-support--1fc66332from
devs/jd/worktree-docs-queue-stack/cross-link-merge-queue-stack-docs--433bc3a8

Conversation

@jd
Copy link
Copy Markdown
Member

@jd jd commented Apr 22, 2026

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

Depends-On: #11235

jd added 2 commits April 22, 2026 20:17
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
@jd
Copy link
Copy Markdown
Member Author

jd commented Apr 22, 2026

This pull request is part of a Mergify stack:

# Pull Request Link
1 docs(merge-queue): document stack support #11235
2 docs(stacks): cross-link to merge queue stack documentation #11236 👈

@mergify mergify Bot had a problem deploying to Mergify Merge Protections April 22, 2026 18:18 Failure
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Apr 22, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 ⛓️ Depends-On Requirements

Waiting for:

This rule is failing.

Requirement based on the presence of Depends-On in the body of the pull request

🔴 👀 Review Requirements

Waiting for:

  • #approved-reviews-by >= 2
This rule is failing.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🔴 🔎 Reviews

Waiting for:

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.
  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 📕 PR description

Wonderful, this rule succeeded.
  • body ~= (?ms:.{48,})

@mergify mergify Bot requested a review from a team April 22, 2026 18:20
@jd jd force-pushed the devs/jd/worktree-docs-queue-stack/document-stack-support--1fc66332 branch from d01d1ff to 67ff744 Compare April 22, 2026 18:21
@jd jd closed this Apr 22, 2026
@jd jd deleted the devs/jd/worktree-docs-queue-stack/cross-link-merge-queue-stack-docs--433bc3a8 branch April 22, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant