GitHub Ships Stacked Pull Requests to Public Preview
Ordered chains of small, focused pull requests can now be reviewed in parallel and merged as one operation.
GitHub rolled stacked pull requests out to public preview on July 30, 2026, making the feature available to all repositories over the following days. A stack breaks one large change into an ordered series of pull requests, where each one represents a single, reviewable layer that targets the layer below it.
Reviewers can look at each layer of a stack independently while still seeing how it fits into the overall change through a stack map, and every existing review, required check, and merge requirement continues to apply to each layer. Once a stack is ready, a team can merge the whole thing — or just the layers that are ready — without leaving the pull request view.
The feature works across GitHub's surfaces: the website, the GitHub CLI (via a new `gh-stack` extension), the mobile app, and with coding agents such as GitHub Copilot. GitHub frames the goal as keeping large changes moving without forcing reviewers to either approve one giant diff or wait on a strictly serial chain of small ones.
GitHub is far from the first tool to support stacked changes — the workflow is long-established in tools like Graphite and in Git-native stacking conventions — but this marks the feature becoming a first-class, built-in part of github.com rather than something layered on top through a third-party tool. Bringing it directly into GitHub removes the need for a separate service just to keep a stack's branches, reviews, and merge order in sync with what GitHub itself treats as the source of truth. Teams that already use a third-party stacking tool aren't required to switch; the built-in feature is additive rather than a deprecation of existing workflows.
Because it's a public preview, GitHub is expected to keep iterating on stack management before the feature reaches general availability; the July 30 changelog entry is the canonical record of what shipped on day one.