This message was deleted.
# report-bugs
s
This message was deleted.
1
p
That's odd - is there a chance that the changes you've pulled down have been merged/closed? Did you do a
gt rs
after doing the
downstack get
?
j
Yeah we did
gt rs
. it is weird that
gt l
doesn't show PR info after
downstack get
Is that expected?
p
no that's not expected - when you downstack get the branch it should show you that PR and all its PRs downstack when you do
gt l
when you do
downstack get
, does the output say
synced <branch> from remote
?
1
j
Waiting for coworker to try again. Will report back
🫡 1
I was thinking potential plan is untrack the stack using
gt branch untrack <bottom branch>
and then retry
gt downstack get <top branch>
. Does that seem reasonable?
p
that sounds reasonable! let me know how it goes
i'm sure you've seen this, but just in case you haven't 🙂
j
does the output say
synced <branch> from remote
?
Yes
Is there a way to start over completely? After branch untrack and downstack get, still wasn't getting PR info. Then we tried
gt dev cache --clear
and then again branch untrack, downstack get, still no PR info, but this time it wasn't getting the entire stack either
Will try again after
gt repo init --reset
p
Ah sorry about that! Roping in @Jacob Gold for visibility
j
After
gt repo init --reset
and
gt dev cache --clear
, then
gt downstack get <top branch>
,
gt l
now showing PR info. Yay!
p
Huh weird. Glad a reset was able to fix it!
j
We added a branch using
gt branch track
selected a parent (top branch). Confirmed
gt l
still showing PR info for parent branches.. but the new branch we just tracked doesn't show PR info. Maybe expected? There is a PR already for the new branch though. Do you recommend
gt ss
or
gt downstack get <the-new-branch>
next?
Wait... it is showing PR info now
Tried again and got the same thing. After
gt branch track
then
gt l
doesn't show PR info initially. Then did
gt ls
and then
gt l
again, and 2nd time showed PR info
j
the GH sync happens in the background to keep commands snappy— perhaps we should fetch data synchronously for track though...
track
just starts tracking the branch locally 🙂