Not exactly sure, but I may have run into a bug caused by Github native stack + Graphite merge queue: How to reproduce: say I have a Graphite stack: main <- A <- B <- C, and out of curiosity, I manually create a Github native stack on the Github webUI as it prompts, then when I merge PR A into main using Graphite merge queue, something weird happens: Graphite creates a temporary PR to run CIs, and then closes PR A and branch A, which immediately causes PR B to be closed as its target branch doesn't exist anymore (not sure why, maybe because Graphite couldn't update the Github stack managed PRs?). So I end up with only PR C targeting branch B, and

gt sync

messes up my local stack as well. How I get myself out of the issue: it's really tricky. I can't reopen PR B since its target branch is gone, and I can't modify the target branch of a closed PR, so the only way out is to create a temporary branch A, manually reopen PR B, and then change its target to main. To recover the local stack, I just

untrack

and then re-

track

(if some branches are out dated, manual rebase can be necessary) . This is probably just user error and "expected" weirdness when mixing Graphite stack with Github stack, but I thought it was worth reporting just in case anyone ran into it as well

Hey There! We have had reports of this previously and it is currently with our team for review. Can I get a PR link where you notices this happen so I can compare the symptoms? Thanks!

As always, thanks for your prompt response 🫡 I couldn't recall the exact PRs as it happened a few days ago - will let you know if I run into it again

Sounds good!