Hi, I've gotten into a bit of a tricky situation. I had a stack like (bottom) a-b-c (top). I created a new branch and moved things around so it was like (bottom) a-b-d-c (top). I ran

gt submit --stack --update-only

and saw an error

ERROR: Failed to submit PR for c: GitHub could not open a PR with the specified base

. I tried to correct this by running

gt submit --stack

. However, now Graphite is in a state where the remote shows that branch c is stacked on b, but my local shows that branch c is stacked on d. I tried to correct this by checking out branch c and running

gt submit -f

, but it said every operation was a no-op and nothing has changed at the remote. How can I tell the remote that branch c has a new parent?

Hey Dane! Sounds like local parent is

d

but GitHub still has

c

based on

b

.

--update-only

won’t create/publish a new mid-stack branch, so retarget can fail if

d

isn’t on the remote yet. Confirm

d

exists remotely, then from the tip try

gt sync

and

gt submit --stack --always

. Still no-op? Paste

gt --version

,

gt ls

, and what GitHub shows as `c`’s base and ill brainstorm some other causes. Thanks!

Thanks!

gt submit --stack --always

worked!