You can also create two separate stacks: A -> B C -> D And then use

gt move

to move one on top of the other (eg.

A -> B -> C -> D

We do not support multiple parents, so a topology like: A B \ / C (child) Will not work

Say that from the first stack, I merge PRs up until B, so the

E

stack can now point to main. What would be the steps to take there to make that change?

And regarding what you wrote in the first message, would that be a single stack? With branch D being based on B, but still being part of that stack? (Essentially meaning that branches in a stack don't have to be based on the newest branch, and can be based on some branch in the middle of the stack)

(Essentially meaning that branches in a stack don't have to be based on the newest branch, and can be based on some branch in the middle of the stack)

Yes this is possible

>> Say that from the first stack, I merge PRs up until B, so the

E

stack can now point to main. What would be the steps to take there to make that change? You can create this through your normal flow. You can create A -> B -> C ->D. Then

gt checkout B

and then create E -> F. Merging and restack is handled by

gt sync

and

gt restack