Stacked pull requests break large changes into small, reviewable pull requests. They’re an ordered series of pull requests that each represent focused layers of your change. With stacks, you can…
Maybe I just don’t know enough how these work, as I’ve never heard of stacked prs before.
What does the workflow look like? Can the first PR be merged and deployed without the other prs being approved and merged first? Or do they all need to be approved and it all gets merged together?
That is the point. By making smaller PRs, you inevitably end up with dependencies between them. So you’d like to stack them.
Maybe I just don’t know enough how these work, as I’ve never heard of stacked prs before.
What does the workflow look like? Can the first PR be merged and deployed without the other prs being approved and merged first? Or do they all need to be approved and it all gets merged together?
I haven’t used it yet but assuming they did it right, yes you can merge the PRs sequentially.
Assuming it’s like gitlab’s stacked PRs, all the merge requests are independent. It’s basically “just” rebasing the stack once the bottom gets merged.