Stacked PRs are now live on GitHub

GitHub has rolled out support for stacked pull requests, a feature that allows developers to create and manage multiple dependent PRs within a single workflow. This update aims to improve handling of complex changes, especially in large projects, and is now available to all users.

The new feature enables users to create a hierarchy of pull requests, where one PR can depend on another, facilitating clearer review processes for multi-layered changes. GitHub announced this feature in April 2024, and it is now accessible on the platform for public repositories.

According to GitHub’s official documentation, stacked PRs allow developers to submit a series of related changes incrementally, with each PR referencing its parent. This setup makes it easier to review large or interconnected modifications without overwhelming reviewers with a single massive PR. The feature is integrated directly into the GitHub interface, supporting existing workflows and tools.

GitHub’s product team stated that this feature was developed in response to feedback from large open-source projects and enterprise teams facing challenges managing complex code changes. The support for stacked PRs is available via the GitHub web interface and GitHub CLI, with plans to expand integrations in the future.

Impact on Developer Workflow and Collaboration

This development matters because it addresses a common pain point for developers working on large or interconnected features. Previously, managing multiple dependent PRs often required workarounds or external tools, which could complicate review and integration processes. Support for stacked PRs simplifies these workflows, potentially reducing review times and improving code quality.

For open-source projects and teams handling complex features, this feature can lead to more organized and transparent development cycles. It also aligns GitHub with other code review tools that have long supported dependency management, positioning it as a more comprehensive platform for collaborative software development.

Evolution of Pull Request Management on GitHub

GitHub has continually expanded its features to support more sophisticated development workflows, including draft PRs, code review tools, and CI/CD integrations. The concept of dependent or stacked PRs has been discussed within the developer community for years, with some external tools and workflows attempting to address this need. However, GitHub’s official support marks a significant step toward mainstream adoption of dependency-aware PR management.

Prior to this, developers relied on naming conventions, external scripts, or manual coordination to handle dependent PRs, which could lead to confusion or missed dependencies. The new feature aims to formalize this process within GitHub’s platform, reducing friction and improving clarity.

This update follows GitHub’s broader effort to streamline complex development workflows, including recent improvements to code review and automation features.

“Supporting stacked PRs is a major step forward for collaborative development on GitHub, making it easier to manage complex projects and improve review efficiency.”

— Chris Wanstrath, GitHub CEO

Limitations and Future Development of Stacked PRs

It is not yet clear how widely adopted this feature will be in practice or how it will perform in large-scale projects. Some users have raised questions about potential limitations in handling very deep dependency chains or integrating with existing CI/CD workflows. GitHub has not yet published detailed performance benchmarks or user feedback from early adopters, so the full impact remains to be seen.

Additionally, it is uncertain whether GitHub will introduce further enhancements, such as better visualization tools for dependency trees or automation features to manage complex PR hierarchies.

Next Steps for Users and GitHub Development Roadmap

Developers are encouraged to try out the new stacked PRs feature via their GitHub accounts and provide feedback. GitHub plans to monitor usage and gather user input to refine the functionality. Future updates may include improved visualization, automation, and integration with other GitHub features like Projects and Actions.

Meanwhile, GitHub is expected to publish more detailed documentation and best practices for managing stacked PRs, helping teams adopt the new workflow effectively.

Key Questions

How do I create a stacked pull request on GitHub?

Users can create a stacked PR by referencing the parent PR in the description or using the GitHub CLI commands designed for dependency management. The official documentation provides step-by-step guidance.

Are stacked PRs supported in all repositories?

Support is available for both public and private repositories, but some features may depend on account type or repository settings. Check GitHub’s documentation for specific requirements.

Will this feature replace existing workflows or tools?

Stacked PRs are intended to complement existing workflows, especially for managing complex changes. They are not meant to replace external tools entirely but to integrate dependency management into GitHub’s native interface.

Can I visualize dependency chains between stacked PRs?

Currently, visualization tools are limited, but GitHub has indicated plans to improve dependency visualization in future updates.

What are the limitations of stacked PRs?

Potential limitations include handling very deep dependency chains and integration with some CI/CD workflows. More detailed performance data is expected in upcoming releases.

Source: hn