GitHub makes stacked pull requests generally available

GitHub has made stacked pull requests generally available, turning a workflow that many large engineering teams already use into a standard github.com feature. The company says stacks let developers split a large change into smaller, dependent pull requests that can be reviewed independently and merged together.

The release matters because the hard part of stacked work is not only creating branches. Teams need review state, rebasing, merge queues and automation to behave predictably as the base branch moves. GitHub says the general availability version keeps approvals in place for unchanged code after a rebase, creates signed replacement commits when rebasing stacks, and lets bypass permissions apply to the lowest unmerged pull request in a stack.

What changed for teams

GitHub says repositories using stacks during the preview saw a 9% increase in merged code compared with peers. It also says more than two thirds of the top 1% of repositories now use stacked pull requests, with a 5% improvement in time to merge. Those are company reported figures, so teams should treat them as directional rather than a guarantee for every workflow.

The new version also changes how stacks land. A stack can enter the merge queue as a single merge group, while merge commit workflows now create one merge commit per pull request instead of flattening the whole group into one commit. GitHub also says stack information is now visible in the pull request header and list view, with keyboard shortcuts for moving between pull requests in a stack.

Why it matters

For developers, the practical value is narrower reviews with less waiting. A database migration, API change and interface update can become separate pull requests while still moving as one sequence. That can make review comments more precise and reduce the pressure to approve a large mixed change simply because part of it is urgent.

The tradeoff is process discipline. Stacks help when teams keep each pull request focused and understand the dependency chain. They can add confusion if reviewers treat the stack as invisible background. CyberOGZ would watch how well the feature works with merge queues, branch protection and automated agents, because those are the places where stacked workflows either save time or create subtle coordination problems.

GitHub says stacked pull requests are available on all github.com plans and will come to GitHub Enterprise Server in a future release.

Sources

• github.blog

Cover photo by Daniil Komov on Pexels, used under the Pexels License.