This message was deleted.

Ahh sorry you're running into this @Ryan Rhee!! We're looking into this now!

i actually merged it using githubs ui and

gt rs && gt sr

heh

Ah ok no worries, keep me posted!

DM’ing you

You can try invalidation of caches.

that worked, thank you!

Hmm ok sorry about that - go ahead and DM me those PRs!

this is how i’m clearing the cache.

@Brendan Ngo took a look at this PR and looks like the stack dependency table is incorrect - if this is blocking, he can go ahead and fix this manually. Otherwise this is a bug that we'll look deeper into!

i made these PRs with “gt ss” and didn’t do anything special. this particular pr is not blocking, but if I create new PRs some of those will end up in this state as well.

the problem I saw was we were missing the first PR in our dependency table so makes sense now if you created it not with Graphite

graphite cli seemed to know the dependency since I used gt track on the first PR. sounds like graphite needs to update the dependency table if a branch is tracked manually, or if a stack is submitted and parts of that stack are not in the dependency table?

I think that's generally true. we update the dependency table on submit which I believe should handle this. Next time you see this can you try

gt ss --always

so force submit updates?

yes, i’ll try that next time and report back. thanks!

also if you have a steady repro please let us know! would love to root cause this if possible. Thanks again for reporting!

i’m pretty sure the repro is: 1. create first PR using github’s vscode integration; using github’s

hub

cli probably also works? 2. create a 2nd PR on top of PR1 using

gt ss

3. (optional) create 3rd PR on top of PR2 using

gt ss

but the next time i do this flow i’ll confirm that it breaks the dependency table.

just verifying you are also tracking the first pr with

gt branch track

?

oh yeah, forgot that part

Thanks for trying! We've filed a ticket for this and will look into. For now you can probably avoid this by creating all your prs with Graphite. Also

gt ss

just submits the prs. Are you using graphite to create/manage your branches also?

i’m creating branches with

gt bc -m ...

the graphite command for renaming a branch is

gt branch rename

(alias

gt brn

)! Note that this removes any associated GitHub pull request.

good to know, thank you!