Skip to content

Draft changelog: Merge Queue stacked PR support #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pv72895 merged 1 commit into from
Aug 4, 2026
Merged

Draft changelog: Merge Queue stacked PR support #307

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions changelog/2026-07-31-merge-queue-stacked-pull-requests.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: "Merge Queue: Stacked pull request support"
description: "Trunk Merge Queue now natively supports GitHub stacked pull requests — enqueue any PR in a stack and Trunk tests and merges the whole stack together."
slug: merge-queue-stacked-pull-requests
date: 2026-07-31
category: Merge Queue
type: new-feature
---

**Trunk Merge Queue is now stack-aware for GitHub's native stacked pull requests.**

Submit any PR in a stack — top, bottom, or middle — using the API, browser extension, `/trunk merge` comment, or the merge checkbox, and Merge Queue takes care of testing and merging each segment. You can even enqueue multiple PRs from the same stack at once; Trunk sorts out the dependencies.

- **Test the whole stack as one block.** Trunk runs CI against the stack collectively instead of PR-by-PR, so you get real throughput and CI-cost wins on stacked work.
- **Track stacks in the queue UI.** A stack submission shows all included PRs together in the Merge Queue view.
- **Submit from anywhere in the stack.** No need to wait for lower PRs to merge before enqueueing higher ones.

See [Stacked pull requests](/merge-queue/using-the-queue/stacked-pull-requests) for details on submission, tracking, and known GitHub-side rebase behavior.
Loading