We have several branches that we were merging to main. We have one single branch, and 3 other branches in a stack. Both stacks had ‘main’ as the PR target branch. We want to change the target branch of each stack to ‘staging’ We have an issue though. When we use

gt move --onto staging

Graphite seems to have updated the git PR to change the target branch. But, no matter what we do, the app.graphite.com stack shows ‘main’ as the target. We have tried to

gt submit --stack

or

gt submit --stack --force

etc, but gt local says “nothing to submit” How can we fix the remote app.graphite.com to change the merge branch for the stack?

i think i'm hitting the same issue. my target always stays the same in the UI (incorrect, original parent), but gt log shows the correct updated parent.

Yes, that’ what I have. And, app.graphite.com shows ‘Needs Restack’ I could merge in github, but then, what happens to my stack..

i believe you have to create a 2nd trunk in

gt config

Hmm. I did add a 2nd trunk, but I did not configure that branch as PR target. Doing that now..

i think there may be a

--target-trunk

flag or other such for

gt submit

(we stopped using multiple trunks recently, my memory has faded — may need to wait for graphite employee guidance if an agent can't figure it out from docs + cli man pages) EDIT: graphite.com/docs/command-reference#:~:text=%2D%2Dtarget%2Dtrunk….

Oh.. that worked. --target-trunk, and i also used --always, since it was telling me it did not need to be udpated.

woo, nice 🙂

Thanks for the assistance Tyler!!