Stacked pull request management
Since Sep 24Updated Nov 10, 2026Based on 21 AI answers
Reviewed by Dimitry Apollonsky
Brands AI mentions
Breaking large pull requests into stacked diffs to speed up reviews
Also mentioned rarely: GitHub Github, Aviator, git-branchless, GitHub CLI Stack Extension, GitHub CLI, Jujutsu, ReviewStack, Sapling, SL Beauty Co, SPR, stack-pr, Bazel, GitButler, GT, Turborepo, Angel Ventures, GitHub Stack CLI, Git, GitHub Actions, git-spice, Stacked Git, GitLab · gitlab.com, Gitlab · gitlab.io, Johnson & Johnson, Sapling · sapling.ai, Stargate Finance
- GraphiteChatGPTChatGPT 100%Google AI ModeGoogle AI Mode 100%
- Git TownChatGPTChatGPT 90%Google AI ModeGoogle AI Mode 45%
- gh stackChatGPTChatGPT 40%Google AI ModeGoogle AI Mode 82%
- GitHubChatGPTChatGPT 60%Google AI ModeGoogle AI Mode 55%
- SaplingChatGPTChatGPT 80%Google AI ModeGoogle AI Mode 18%
Graphite leads this topic, but GitHub Copilot leads AI Developer Productivity Tools overall.
Questions and answers
Google AI ModeNov 8, 2026
Managing stacked pull requests (PRs) has become drastically smoother with
native platform support and dedicated CLI tools. Instead of manually juggling rebase conflicts and target branches across a chain of commits, modern tooling automates the heavy lifting.The top options range from native platform features to standalone CLI utilities and web-backed platforms:
1. GitHub Native &
gh stack(Official)GitHub recently rolled out native support for Stacked Pull Requests across all plans, removing much of the historical friction of dependent branches.
- Key Features: Persistent stack context headers right in the PR UI, automated rebase handling that preserves approvals, auto-merge options, timeline events for stack membership, and
Shift + J/Shift + Kkeyboard shortcuts to jump between PRs in a stack. - CLI Tool (
gh stack): The official extension for the GitHub CLI lets you initialize, submit, sync, rebase, and navigate stacks locally. - Get Started: Install via the terminal with
gh extension install github/gh-stackand check out the Stacked Pull Requests CLI Commands Documentation . Read more on the GitHub Blog Changelog.
2. Graphite (
gt)Graphite is one of the most mature, heavily praised commercial/CLI ecosystems built specifically for stacked diffs and fast code review.
- Key Features: Fast CLI (
gt), a sleek web app to visualize entire stacks of dependent PRs, automatic trunk-based rebasing when lower PRs change or merge, and rich review UI that makes reviewing multi-commit or multi-PR chains intuitive. - Best For: Teams that want a dedicated, high-velocity UX layer on top of GitHub with minimal mental overhead for rebasing.
- Get Started: Explore workflows and installation steps directly on Graphite.dev.
3. Aviator (
av) & Stacked Git (stg)For teams looking for open-source or deep merge-queue integrations:
- Aviator (
av): Focuses heavily on enterprise scale, combining stacked PR management with automated merge queues so dependent chains land safely without breaking main. Learn more at Aviator.co. - Stacked Git (
stg): A classic, patch-based Git extension that manages a stack of patches directly inside Git's index rather than traditional branching, appealing to developers who prefer a lower-level, patch-centric mental model.
Quick Comparison of Workflows
Tool / Option Best For Primary Interface Rebase / Sync GitHub gh stackNative GitHub users wanting zero-config platform integration CLI ( gh stack) + GitHub UIAutomatic / Semi-automated via CLI Graphite High-velocity engineering teams needing visual UI & speed CLI ( gt) + Web DashboardAutomatic background rebasing Aviator Enterprises requiring strict merge queues with stacks CLI ( av) + Web / GitHub AppIntegrated merge-queue rebase Stacked Git ( stg)Kernel/patch-style workflow enthusiasts Pure CLI / Git subcommand Manual patch-stack shifting Are you currently using GitHub, GitLab, or Bitbucket , and do you prefer an official/lightweight CLI (like
gh stack) or a visual web dashboard (like Graphite)?ChatGPTNov 8, 2026
There are several strong tools for creating and managing stacked pull requests (stacked PRs), ranging from lightweight Git CLI utilities to full-featured platforms with automated rebasing, dependency tracking, review orchestration, and intelligent CI execution.
My recommendation: If you're dealing with complex dependencies, frequent rebasing, parallel development, or multiple contributors working on interdependent changes, evaluate Graphite and GitHub's native
gh stackfirst.Here's how the options compare.
1. Best tools for stacked pull requests
1. Graphite
(Best overall for advanced stacking)
Commercial platform · GitHub integration
Graphite provides a dedicated workflow for creating, navigating, updating, and merging stacked PRs.
Key capabilities:
- Automatically restacks dependent branches after changes.
- Visualizes PR stacks and their relationships.
- Supports parallel development and review.
- Automated stack merging.
- Merge queue with parallel CI and batching.
- CI optimizations to avoid redundant test runs.
Particularly useful when many developers work on interconnected changes.
Website: graphite.com ·
www.graphite.comgraphite.comwww.graphite.com
2. GitHub gh stack
(Best native GitHub option)
Open source · GitHub CLI
GitHub now has first-class support for stacked pull requests, including a CLI extension.
Key capabilities:
gh stack initcreates a stack.gh stack addadds dependent branches.gh stack rebasecascades rebases through the stack.gh stack submitcreates or updates PRs.gh stack syncsynchronizes local and remote stacks.gh stack modifylets you insert, reorder, fold, or remove branches.- Visual stack maps in the GitHub PR interface.
Particularly attractive if you want to avoid introducing another commercial platform.
Website: GitHub gh-stack ·
github.comdocs.github.comdocs.github.com
3. Git Town
(Best for multi-platform teams)
Open source · Git CLI
Git Town automates high-level Git operations and branch management.
Key capabilities:
- Create and manage dependent feature branches.
- Synchronize branches with upstream changes.
- Manage branch relationships.
- Automate proposing and cleaning up branches.
- Supports GitHub, GitLab, Bitbucket, Gitea, and Forgejo.
Particularly useful when you want a consistent branching workflow without committing to a GitHub-specific platform.
Website:
4. Sapling
(Best for complex source-control workflows)
Open source · Source control system
Developed at Meta, Sapling is designed to make large repositories and stacked changes easier to manage.
Key capabilities:
- Native stacked-change workflows.
- Easier navigation between dependent changes.
- Efficient rebasing and history manipulation.
- Git repository interoperability.
- Integration with GitHub PR workflows.
Worth evaluating for large engineering teams and complex repositories.
Website:
5. Jujutsu (jj)
(Best for flexible dependency management)
Open source · Version control
Jujutsu takes a different approach to version control, making it easier to manipulate changes and work with complex histories.
Key capabilities:
- Change-oriented version control.
- Flexible rebasing and history editing.
- Easier management of dependent changes.
- Git interoperability.
- Can connect with GitHub's native stacked PR functionality.
Particularly interesting if you want to improve the underlying development workflow, not just PR management.
Website:
github.comdocs.github.comdocs.github.comdocs.github.com
2. Tools for accelerating complex dependencies
Managing stacks is only half the problem. The bigger challenge is minimizing the time spent waiting for dependent changes, rebasing branches, resolving conflicts, and rerunning CI.
These complementary tools and techniques can make a substantial difference.
Capability Recommended solution Benefit Automated restacking Graphite, gh stackUpdates dependent branches automatically Dependency visualization Graphite, GitHub Makes PR relationships visible Parallel CI execution Graphite Merge Queue Reduces sequential waiting CI caching Bazel, Turborepo Avoids redundant work Merge orchestration Graphite Merge Queue, GitHub Merge Queue Controls safe merge ordering Branch synchronization Git Town, gh stack syncKeeps dependent branches current Change manipulation Sapling, Jujutsu Makes complex history changes easier Particularly important: CI acceleration
Consider a stack with five dependent PRs:
main └── PR 1: Database schema └── PR 2: Backend services └── PR 3: API endpoints └── PR 4: Frontend integration └── PR 5: TestsA conventional workflow can require sequential rebasing and repeated CI execution.
There are three useful optimizations:
- Parallel CI: Run independent checks concurrently instead of waiting for each PR to finish sequentially.
- Selective CI: Run expensive tests only on relevant stack layers.
- Merge batching: Combine compatible changes into batches to reduce repeated validation.
Graphite offers stack-aware CI optimizations and a merge queue with parallel CI, fast-forward merging, and batching. GitHub also supports native merge queues for stacked PRs.
3. Comparison: Which should you choose?
Tool Stack management Automated rebasing Advanced CI Best fit Graphite Excellent Yes Excellent Advanced teams GitHub gh stackExcellent Yes Via Actions GitHub teams Git Town Very good Yes External CI Multi-forge teams Sapling Excellent Yes External CI Large codebases Jujutsu Very good Yes External CI Advanced developers These are qualitative assessments, not benchmark scores.
4. My recommended architecture
For a team dealing with substantial dependency chains, I'd consider this combination:
Stacked PR automation architecture
Development and branching
Graphite or GitHub gh stack
Dependency and stack management
Automatic rebasing, restacking, PR relationships
CI optimization
GitHub Actions + Bazel or Turborepo caching
Merge orchestration
Graphite Merge Queue or GitHub Merge Queue
Validated changes land in main
One architectural consideration: stacked PRs are naturally a linear dependency chain. If your project has a complex dependency graph with multiple independent branches converging on shared changes, use multiple stacks and a merge queue rather than forcing everything into one stack.
GitHub's native implementation also has some constraints: all branches must be in the same repository, and GitHub Desktop does not support the stacked PR workflow.
5. A few questions to narrow down the best solution
The best option depends on whether you're optimizing individual developer productivity or coordinating a large dependency graph across an engineering organization.
1. Where is your source code hosted?
GitHub
GitLab
Bitbucket
Multiple platforms
2. What's the approximate team size?
Solo developer
5–20 developers
20–100 developers
100+ developers
3. What's your biggest priority?
Automated dependency management and restacking
Parallel CI and faster merges
Visualizing complex PR dependency graphs
Automating PR creation and review
End-to-end workflow orchestration
4. Who or what is creating the pull requests?
Human developers
AI coding agents
Both developers and AI coding agents
[Find my best tooling architecture]
I can use those answers to put together a more targeted shortlist, including tools that automate dependency resolution, coordinate parallel PR stacks, and reduce end-to-end development and merge time.
Pages cited in this answer16
- graphite.comGraphite - Code review for the age of AI
- graphite.comEvaluating Tools For Stacking - Graphite
- graphite.comCI Optimizations - Graphite
- graphite.comMerge Queue Optimizations - Graphite
- graphite.comMerge Queue
- github.comGitHub - github/gh-stack: GitHub Stacked PRs · GitHub
- docs.github.comAbout stacked pull requests - GitHub Docs
- github.comgh-stack/docs/src/content/docs/introduction/overview.md at main · github/gh-stack · GitHub
- docs.github.comManaging stacked pull requests - GitHub Docs
- git-town.comIntroduction - Git Town 24.0
- docs.github.comUse other tools with stacked pull requests - GitHub Docs
- faun.devBest Stacked Pull Requests tools: ranked and compared
- sapling-scm.comSapling from Meta | Sapling
- jj-vcs.github.ioJujutsu docs
- graphite.comCI Optimizations - Graphite
- docs.github.comStacked pull requests - GitHub Docs
- Key Features: Persistent stack context headers right in the PR UI, automated rebase handling that preserves approvals, auto-merge options, timeline events for stack membership, and
Also asked as
- I need to manage and create stacked pull requests. Are there any tools that can help me accelerate my workflow when I have complex dependencies?
- I am looking for software to handle stacked pull requests. What tools can help me speed up my workflow when I have complex dependencies?