Allow cascade PRs

[kvaster]

Feature Description

Sometime you need to have 'cascade' PRs. i.e.

• first you're working on feature A (derived from main branch) and you create PR feature A -> main
• next you need to work on feature B, but this feature depends on changes of feature A and it's corresponding PR is not yet approved. The best way to work on such feature is derive from feature A and later you need to create PR feature B -> feature A.

Currently second PR will be automatically closed on feature A merge and branch delete. It would be helpfull to rebase second PR. i.e. change 'feature B -> feature A' to 'feature B -> main' when first 'feature A -> main' is merged and 'feature A' branch is deleted.

Screenshots

No response

[lunny]

Could you reopen it and rebase to main?

[kvaster]

It's not possible to reopen and rebase PR: This pull request cannot be reopened because the branch was deleted.

[lunny]

Then you can check out the pull request and create a new one.

[kvaster]

Then you can check out the pull request and create a new one.

You may, but review in-progress will be lost in this case.

[LeafyLappa]

Then you can check out the pull request and create a new one.

You may, but review in-progress will be lost in this case.

came across this exact problem, very frustrating.

[xav-ie]

Re-opening is not an option because my team will spend time reviewing that PR and all the comments and discussion dissappear on re-open.

[xav-ie]

gh pr merge has same issue cli/cli#8331 ... maybe they are connected?

[denyskon]

Closing in favor of #27062 which will soon be fixed by #28539