It depends on how long you expect this to be a problem for — if the fix is simple you could also create a new graphite branch with the fix based on main, and then move your branches onto that one

Another solution is from main to run

git reset --hard @~<n>

and then refrain from `repo sync`ing for a little

ohh good idea, revert my

main

do you expect issues if I restack onto a prior commit?

and also accidentally repo syncing will just bring you back to broken state, which could be annoying

but I reset main, and

stack restack

is saying I don't need to restack my branches

(if you

gt log

, do you see too many commits)

it's almost like Graphite isn't picking up on me rewinding

main

locally

brb in a few hours, and

main

will probably be resolved by then, but this might be showing us a CLI bug

or whatever registry Graphite uses to keep track of what's associated with what

i was looking at this code yesterday

repo sync again should fix, probably avoid the reset solution for now 😬