GitHub Launches Stacked Pull Requests for Cleaner Code Evaluations

GitHub has launched a brand new function known as Stacked Pull Requests, designed to simplify the evaluation course of for giant code modifications. Presently in non-public preview (as of August 4, 2026), Stacked PRs enable builders to interrupt huge pull requests into smaller, centered layers that may be reviewed and merged independently. This method not solely reduces reviewer fatigue but additionally accelerates suggestions and deployment.

Historically, builders have confronted a painful trade-off: submit one monumental pull request that’s not possible to evaluation successfully, or handle a sequence of smaller pull requests manually, usually resulting in conflicts and logistical complications. Stacked PRs goal to remove this dilemma by introducing construction by way of dependency chains. Every pull request in a stack builds on the one beneath it, so reviewers solely must give attention to the incremental modifications in every layer.

How Stacked Pull Requests Work

GitHub’s workflow organizes a big function into discrete layers, every scoped to a single concern. For instance, a brand new product search function is perhaps break up into:

• Layer 1: Information mannequin setup
• Layer 2: API creation
• Layer 3: Backend integration
• Layer 4: Frontend person interface

Every layer is dependent upon the earlier one, permitting reviewers to give attention to smaller, logically grouped modifications. GitHub additionally offers CLI help through the gh-stack extension, which helps builders create, handle, and rebase these stacks straight from their terminal.

The method additionally integrates seamlessly with GitHub’s CI/CD workflows. Modifications in decrease layers mechanically cascade by way of the stack, prompting updates and revalidation of dependent layers. This ensures that every layer stays secure and prepared for evaluation.

Brokers and Automation in Stacked PRs

As AI coding brokers turn into more and more prevalent—Gartner initiatives a 50% productiveness acquire throughout the software program growth lifecycle by 2028—GitHub has tailor-made Stacked PRs to accommodate them. These brokers could be educated to decompose duties into stackable layers, deal with validations, and even handle rebase conflicts inside the stack. This automation might additional scale back human bottlenecks, particularly for giant groups transport complicated options.

Why This Issues

Stacked pull requests aren’t a completely new idea; comparable workflows have been popularized by instruments like Phabricator, Graphite, and Git City. Nevertheless, GitHub’s implementation is notable for integrating the workflow straight into its platform, alongside its current pull request and CI techniques. This might make Stacked PRs the default for groups already utilizing GitHub, particularly because the function matures and strikes out of personal preview.

For builders, the advantages are clear: smaller, focused evaluations result in higher-quality suggestions, quicker merges, and fewer last-minute surprises throughout deployment. For organizations, the structured method can enhance growth velocity and scale back expensive delays attributable to under-reviewed code.

What’s Subsequent?

Whereas Stacked PRs are presently in non-public preview, GitHub is predicted to roll out broader availability within the coming months. The corporate has additionally partnered with instruments like Devin to develop help, additional embedding this workflow into the developer ecosystem. Because the automation and AI integration enhance, Stacked PRs might turn into a cornerstone of contemporary software program supply pipelines.

Builders involved in making an attempt out Stacked PRs can discover GitHub’s documentation for setup steerage and CLI instructions. With productiveness positive factors on the desk, this function could considerably reshape how groups deal with large-scale coding initiatives.

Picture supply: Shutterstock