GitHub’s new Stacked Pull Requests feature restructures how developers submit and review changes by allowing large code updates to be broken into smaller, interdependent units.
With Stacked PRs, each unit can be reviewed and merged individually while still contributing to the overall feature set. The approach helps developers shift away from monolithic pull requests, which have become increasingly difficult to manage as development continues to move faster.
The release of Stacked PRs is a response to the rise of AI-assisted coding tools, which have greatly increased the volume and scale of code submissions, placing new pressure on review workflows. While large pull requests spanning dozens of files used to be merely inconvenient, they are sometimes now a systemic issue. There is a widening gap between code generation and code review, with reviewers dealing with reduced visibility and slower turnaround times.
With the layered workflow of Stacked PRs, developers can sequence related changes so that each pull request builds on the previous one. Reviewers, in turn, assess smaller, focused diffs while maintaining visibility into how each piece contributes to the overall change. The structure allows teams to merge either individual components or entire stacks, depending on readiness.
Building on Earlier Solutions
Similar workflows, often described as “stacked diffs,” were popularized in earlier code review systems. These systems addressed the same issues around reducing wait times for reviews while preserving development momentum. GitHub’s move brings this model into its native platform, reducing the need for third-party tools that previously filled the gap.
This offers big advantages, particularly for companies managing large codebases and monorepos. In these environments, development can be modular, with teams working on interconnected components in parallel. Traditional pull request models often forced developers to choose between waiting for upstream changes to merge or bundling work into large, unwieldy submissions. Stacking introduces a middle path, enabling incremental progress without sacrificing structure.
GitHub has paired the feature with a command-line extension that automates much of the underlying workflow, including branch management and rebasing. On the interface side, stacked changes are presented visually, allowing reviewers to navigate the hierarchy of updates and understand dependencies between them. This integration of CLI and UI is intended to lower the barrier to adoption.
Cultural Shift
The technical implementation of Stacked PRs may prove easier than the cultural shift required to use it effectively. Developers must reorganize how they structure their work, breaking features into logically discrete units that can stand on their own. This could be a challenge for teams accustomed to broader, less segmented workflows.
This release will likely cause some competitive disruption. By embedding stacked workflows directly into its platform, GitHub is encroaching on tools that built their value around this capability. Vendors that previously offered stacking as an extension to GitHub must now differentiate beyond core functionality.
More broadly, the feature is a recalibration of development priorities. As AI systems speed up code production, the limiting factor is no longer writing software but validating it. Review workflows, once secondary, are becoming central to maintaining quality and stability.