This message was deleted.

You can run

gt sync && gt restack

on the middle branch & then re submit via

gt submit

.

Ah! I wasn't `gt submit`ting again.

This will reset the base branch of the middle branch:

gt sync && gt restack

, and communicate with Github that this changed:

gt submit

Is there any situation where the base gets approved and merged and you wouldn't want to sync and restack? As someone who was hit by a badly merged stack as a first time user because I didn't know to do these things, I'm baffled that the VS Code extension (or gt itself) didn't just do this automatically behind the scenes.

> Is there any situation where the base gets approved and merged and you wouldn't want to sync and restack? Yeah in the past we attempted to rebase the rest of the stack after the base merged, but this can get complicated when you are collaborating on a branch.

Speaking as a new user, I'd say this area still needs love from product and ux, because of the importance of that first stack merge experience