GitHub is rolling out Stacked PRs, a new workflow designed to make complex pull requests easier to review and merge. The feature is aimed at teams dealing with bigger code submissions, especially as AI-assisted development keeps increasing the volume of changes developers send for review.
Instead of forcing reviewers to dig through one massive pull request, Stacked PRs breaks work into smaller dependent pieces. GitHub says this makes reviews faster, keeps feedback more focused, and reduces the merge conflicts and context loss that often come with oversized PRs.
How the Workflow Works
With Stacked PRs, each pull request in a stack is based on the branch before it. GitHub tracks those relationships automatically, so when an earlier PR changes, dependent PRs can be updated without developers manually rebasing every branch.
The workflow is supported through gh-stack, an extension for GitHub CLI that handles branch creation, rebasing, pushing, and opening pull requests against the correct base branch. On GitHub’s web interface, reviewers can move through the stack step by step, with each layer shown as its own focused diff and still subject to the usual checks and policies.
Developers can merge individual pull requests or the whole stack, including through the merge queue. After a merge, the remaining PRs are automatically rebased so the next one in line points to the correct base branch.
Why GitHub Is Doing This
The timing reflects a wider shift in software development. AI tools are producing more code than before, and that makes traditional review workflows harder to scale. At the same time, monorepos and platform engineering are pushing teams toward more modular, parallel development patterns that fit stacked workflows better.
According to analyst Pareekh Jain, the old PR model often created a bottleneck: developers either waited too long for review or bundled too much work into a single PR. Stacked PRs gives teams a way to split a feature into logical layers, such as database, API, and UI work, so each part can be reviewed incrementally while development continues in parallel.
Jain also argues that the biggest benefit is the reduction of “rebase hell,” where teams spend too much time updating dependent branches after base changes. Because GitHub now integrates the workflow into both the CLI and the UI, adoption may be easier than with third-party tools.
What It Means for Teams
For enterprises, especially those working in monorepos, Stacked PRs could make code review less painful and more predictable. Smaller pull requests are easier to understand, easier to test, and less likely to slow down an entire engineering team.
The feature also fits GitHub’s broader response to AI-era development, where the challenge is no longer just writing code faster, but reviewing and integrating it without creating process bottlenecks
