GitHub Stacked PRs (github.github.com)

Article summary

GitHub has introduced Stacked PRs, a feature that allows developers to arrange pull requests in an ordered stack and merge them all in one click. This feature aims to simplify the process of managing large and complex changes by breaking them down into smaller, focused pull requests. Stacked PRs can be managed through the GitHub UI, API, or CLI, and also integrate with AI agents. The feature is currently in private preview and requires sign-up for the waitlist.

Main themes

• Stacked PRs
• GitHub features
• Code review
• Monorepos
• Microservices
• Git workflow

What commenters say

• Stacked PRs are mainly useful for monorepos or long-lived feature/refactor branches, as they allow for coordinated merging of multiple pull requests.
• The feature is seen as a solution to the problem of large and complex pull requests, which can be difficult to review and merge.
• Some commenters argue that stacked PRs are not necessary and that a series of well-organized commits in a single branch can achieve the same result.
• Others see stacked PRs as a way to encourage more organized commits and better code review, by allowing reviewers to focus on individual commits rather than a large changeset.
• There is a desire for the feature to support stacked PRs across multiple repositories, which is currently not possible.
• Some commenters are concerned about the reliance on the GitHub CLI, while others appreciate the integration with AI agents.
• The feature is seen as an improvement over the traditional GitHub PR flow, which can be cumbersome for complex changes.
• There is a discussion about the potential for stacked PRs to replace long-lived feature branches and improve the overall development workflow.