How stacked pull requests break down large code changes
Summary
Stacked pull requests are now officially in public preview on GitHub. Instead of opening one giant PR that takes forever to review, you can break large code changes into an ordered chain of focused la
Related topics
Transcript Excerpt
Stack pull requests are now in public preview on GitHub. Picture this. You have a giant change. So you can either drop one giant pull request that nobody wants to review or you split it across branches that you have to rebase manually forever. With stacks, what you can do is break that change into an ordered series of small pull requests. [music] And each one is a focused layer targeting the layer below it. Open anyone and you only see the diff for that layer with a stack map showing how it fits in. So your team reviews layers in parallel without blocking each other. Then when you're ready, merge the latest ready pull request and it lands that one plus every unmerged layer below it or land just part of the stack and the ones above stay open and automatically rebase. Your existing reviews, …