TL;DR
GitHub has officially released its new stacked pull requests feature, enabling developers to organize multiple related PRs into a single stack. This development is expected to improve workflow management for open-source and enterprise projects.
GitHub has officially launched its new stacked pull requests feature, now available to all users, allowing developers to organize multiple related pull requests into a single stack. This update aims to improve workflow management, especially for complex projects involving multiple interdependent changes.
The stacked PRs feature was announced by GitHub in early 2024 and is now accessible to all users on the platform. It enables developers to create a hierarchy of pull requests, where related changes are grouped into a stack, simplifying review processes and reducing clutter in repositories.
According to GitHub’s official blog, this feature is designed to help teams manage complex workflows, particularly when multiple PRs depend on each other or need to be reviewed in sequence. Developers can now create, view, and manage multiple PRs as a single stack, making it easier to track progress and coordinate reviews.
GitHub has stated that the feature is integrated into existing pull request workflows with minimal disruption, and users can toggle between stacked and individual PR views. The rollout is gradual, with full availability expected across all accounts by the end of March 2024.
Enhanced Workflow Management for Developers
This development matters because it addresses longstanding challenges in managing complex code changes across large projects. By enabling multiple PRs to be grouped and reviewed together, the feature can streamline collaboration, reduce review overhead, and improve project organization. It is especially relevant for open-source projects and large enterprise teams handling interdependent feature sets.
Industry experts suggest that stacked PRs could lead to faster review cycles and fewer merge conflicts, ultimately accelerating development timelines. However, some teams may need time to adapt their workflows to fully leverage this new tool.

Git and GitHub for Beginners: Learn Version Control, Branching, Commits, Pull Requests, and Real Developer Workflow Step by Step (Computer Programming Made Easy)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Previous Efforts to Improve PR Management
Prior to this release, developers relied on manual methods such as referencing related PRs in comments or using external tools to manage dependencies. GitHub had introduced other features like draft PRs and dependency graphs, but these did not fully address the complexity of managing multiple related PRs.
The concept of stacked or hierarchical PRs has been discussed in developer communities for years, with some third-party tools offering similar capabilities. GitHub’s official support marks a significant step toward integrating this functionality directly into the platform, aligning with industry trends toward more integrated development workflows.
The rollout follows earlier beta testing phases, where selected users provided feedback on usability and integration. GitHub has indicated that the feature is now ready for general use, with ongoing improvements based on user input.
“The stacked pull requests feature is designed to make managing complex workflows more straightforward and efficient, reducing review friction and improving project clarity.”
— GitHub Engineering Team

Claude Code for Software Development: Hands-On Guide to AI Coding Workflows, Code Review, Debugging, Testing, and Developer Productivity
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About Stacked PRs Adoption
It is not yet clear how widely adopted the stacked PRs feature will become, or how it will integrate with existing third-party tools and workflows. Some users have expressed concerns about potential learning curves or compatibility issues with their current processes. Additionally, the long-term impact on review quality and project management remains to be seen, as real-world usage continues to unfold.

Ultimate Salesforce LWC Developers’ Handbook: Build Dynamic Experiences, Custom User Interfaces, and Interact with Salesforce data using Lightning Web … Tools Specialist — Jira & Salesforce)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Developers and GitHub
GitHub plans to gather user feedback over the coming months to refine the stacked PRs feature further. Developers are encouraged to experiment with the new tool and share their experiences. Future updates may include enhanced UI options, better integration with automation tools, and expanded support for complex dependency management. The company also intends to monitor adoption rates and address any emerging issues promptly.

Automating Workflows with GitHub Actions: Automate software development workflows and seamlessly deploy your applications using GitHub Actions
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How do I create a stacked pull request on GitHub?
Once the feature is enabled on your account, you can create a new PR and select the option to add it to an existing stack or create a new stack from related PRs. The interface guides you through linking PRs into a hierarchy.
Can I convert existing PRs into a stack?
Yes, users can organize existing PRs into a stack by linking them through the new interface, although this process may vary depending on your repository setup and GitHub updates.
Will this feature be available on all GitHub plans?
GitHub has stated that the stacked PRs feature will be available to all users, with rollout phased over the coming weeks. Specific plan restrictions are not yet detailed.
Does this improve review efficiency?
According to GitHub, grouping related PRs into stacks is intended to streamline review processes, especially for complex, interdependent changes, though real-world benefits may vary by team.
Source: hn