GitHub stacked PRs are now available

By GitHub

Categories: Product, Tools

Summary

GitHub Stacked PRs eliminate massive pull requests by letting each PR target the branch below it instead of main, enabling parallel development without waiting for merges. This architectural shift reduces review time, simplifies debugging, and cuts code misunderstandings—a fundamental workflow improvement for teams shipping faster.

Key Takeaways

  1. Stack PRs vertically rather than all targeting main: bottom PR merges to main, next layer builds on that foundation, creating dependency chains that enable parallel work without blocking.
  2. Reviewers can merge individual PRs incrementally or the entire stack at once, providing flexibility in code integration velocity and reducing bottlenecks from waiting on single approvals.
  3. Smaller, focused PRs in a stack dramatically improve code review quality: reduced cognitive load per PR, faster review cycles, and fewer misunderstandings compared to monolithic 500-line changes.
  4. Developers can continue building features without waiting for previous PR merges, enabling continuous progress on dependent features through layered stacking architecture.
  5. Use stacked PRs for multi-layer features (backend → styling → UI enhancements) to isolate each concern logically and make rollback/debugging granular rather than all-or-nothing.

Related topics

Transcript Excerpt

Today at GitHub, we're announcing GitHub Stacked PRs. Have you ever been building a project and thought to yourself, I'm just gonna add this one feature. Then you notice a bug nearby and decide to fix that. You probably add a few more improvements to help the UI look better, and then suddenly your small change has turned into a massive PR. Large PRs are slower to review, harder to debug, and oftentimes lead to more misunderstanding. That's where Stacked PRs help. With Stacked PRs, each pull request targets the branch right below it instead of every branch targeting main. The bottom PR goes to main, the next builds on that, and the next builds on that one. Let's take a look at some examples. For this example, I want to build a blog in three clean layers. The post, the styling, and then addi…

More from GitHub