GitHub Launches Stacked Pull Requests to Manage AI-Accelerated Code Reviews

GitHub has introduced stacked pull requests as a public preview feature, enabling developers to split substantial code modifications into a series of interconnected, smaller pull requests that reviewers can assess and merge in sequence without waiting for the complete feature to finish.

The feature directly addresses a widening gap in modern development: AI coding tools can now produce production-grade code in minutes, yet code review remains predominantly manual and time-intensive. As generation velocity accelerates, review capacity has become the constraining factor.

How Stacked Pull Requests Work#

Instead of requesting review on a massive pull request containing thousands of lines, developers can organize their work as a logical chain—each PR building on the last. Each request can represent a distinct component: adding a new API endpoint, modifying a database schema, or rolling out a particular business feature. Reviewers examine each piece independently, cutting through the cognitive overload of simultaneous, unrelated changes.

The approach integrates seamlessly with existing GitHub workflows: branch protection rules, review requirements, and merge policies all continue to function as before.

Developer and Reviewer Benefits#

Smaller, focused pull requests tend to be easier to understand and validate, lowering the likelihood that reviewers will miss problematic changes. Developers also gain: they can keep building on top of their own work while earlier layers await review, avoiding the delays that typically require a single massive batch review before development can resume.

This approach also reduces the pain of long-lived feature branches, which often accumulate merge conflicts and stale code. It encourages teams to think of software changes as incremental improvements to the architecture rather than monolithic deliveries—a pattern linked to lower risk and quicker feedback cycles.

Not New, but Now Native#

Stacked development itself is not novel. Meta popularized this workflow internally as "stacked diffs," and startups like Graphite have built entire platforms around it. Until now, teams adopting the pattern relied on third-party tools or manual branch management. By baking stacked PRs directly into GitHub, Microsoft removes much of the friction that kept it from mainstream adoption.