This message was deleted.

two points here — 1. we restack everything because we aren't currently that smart about looking at which branches are actually reordered, we just assume everything down to trunk could have changed 2. as it stands, today we just assume that you'd always want to restack everything as much as possible, and as a result, many commands don't have

--no-restack

options. we have plans to build a

gt pin

command that marks a branch as "shouldn't be restacked by anything", not sure when we will release that at this point though. workaround for your current case is to use two

gt move

commands:

gt co D
gt move -o B
gt co C
gt move -o D

as this won't include all the branches down to trunk in the list of branches to restack

1. this makes sense, i figurd something similar was happening 2. thanks for the workaround! i noticed that 😄 I think my wider problem is that i have had a few times now where I'm working on top of someone else's work. This means that most of the commands don't quite work how i'd want them to because i'm only really working on part of the stack (e.g. push PRs for all of my branches, sync all of my branches on to A, etc) so i've been resorting to a lot of

gt sync --only

I feel like the solution might be making A my trunk? that worked well for development last time, but then things got super messed up once that trunk branch was merged to master, so I'm not sure.

yeah, i think that

gt pin

will solve this exact case, you'd pin

A

, and then it would never be updated

Nice!

yeah, a `pin`ned branch would still

get

, it just wouldn't

restack

(and likely block you from

modify

or

submit

)

sounds perfect - looking forward to it!