[pierrekin]

We use this feature extensively at $dayjob.

Imagine you have some task you are working on, and you wish to share your progress with people in bite sized chunks that they can review one at a time, but you also don’t want to wait for their reviews before you continue working on your task.

Using a stacked set of PRs you can continue producing new work, which depends on the work you’ve already completed, without waiting for the work you’ve already completed to be merged, and without putting all your work into one large PR.

[Gigachad]

I've always done this by just creating new PRs that are based on the branch of the old one. Maybe this is a UI improvement?

[steveklabnik]

Yes, you can do that, but there's lots of things about it that are awkward. This makes it a more first-class feature.

[literallyroy]

Yeah that is a “stacked” pr. The tooling is nice especially when have a larger stack and make changes to the first branch. Update refs + push all branches, same with merging and rebasing onto main.

[philwelch]

You can review PR’s commit by commit, and you can ask people to review PR’s commit by commit. Not a big deal.

[pierrekin]

Then you lose the ability to merge the portion of work which has been agreed to, until the whole change overall has been agreed to.