This message was deleted.

if you don't open a PR from your feature branch to trunk, stack merge will target the feature branch instead — to do this on the CLI, you'll need to set your trunk branch via

gt repo init --trunk <feature>

and then treat the feature as if it were trunk locally — our overall support for this flow isn't amazing right now, so there may be other things that look a little weird in this case. we've talked about building better support for multi-trunk, it likely wouldn't ship until at least the end of this year

Sounds good, some of our devs have done that as a work around. In my case I’m usually floating multiple stacks that are targeted at the true trunk so re-init wouldn’t be an option. multi-trunk sounds like the long term solution for my case.

Yeah, another thing I've thought about that might make this easier a little bit sooner is the option to delete stack dependencies manually from the UI — this would allow you to remove the link from

main

to your feature branch to end up with essentially the same result

Ooo, so you merge a child into another child and then delete it via the UI. This would lead to

gt rs --restack

appending the orphan to the next parent? (Imagining a 3 branch stack and merging the middle one).