Skip to content

merge queue: embarking main (d237e3c) and #11235 together#11244

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/4d0e84fd2e
Closed

merge queue: embarking main (d237e3c) and #11235 together#11244
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/4d0e84fd2e

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 23, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (d237e3c) and #11235 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11235.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: d237e3cf21175e2032fddc9da7d186c139e48ed2
previous_failed_batches: []
pull_requests:
  - number: 11235
    scopes: []
scopes: []
...

jd and others added 2 commits April 22, 2026 20:21
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
@mergify mergify Bot deployed to Mergify Merge Protections April 23, 2026 09:12 Active
@mergify mergify Bot closed this Apr 23, 2026
@mergify mergify Bot deleted the mergify/merge-queue/4d0e84fd2e branch April 23, 2026 09:14
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