https://linen.dev logo
Join Slack
Powered by
image.png
# report-bugs
t
image.png
✅ 1
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using 
gt feedback --with-debug-context <any message>
t
gt get 1234 --force
used to get the parent tracking from remote
Now it fails in the same way as it does without the 
--force
flag
p
hey tyler, can you run 
gt feedback --with-debug-context <message>
so i can take a look at whats happening in our logs? we did release 1.8.4 today which included an update to 
gt get
. are you running on the newest version or are you on 1.8.3 still?
t
Still on 1.8.3, it seems
p
thanks! i'll take a look into it and get back to you
--force
does re-pull parent tracking from remote but only on the code path 
gt get
takes when the PR isn't already cached locally. Because #8382 is cached on your machine with a local branch that isn't Graphite-tracked, 
gt get
takes a different path that hits the tracking check first and bails before 
--force
gets applied. Running 
gt track --parent <parent>
once will get you back on the happy path. this also happens to our own engineering team and there's a ticket that's in progress right now on how we handle branches not tracked yet by graphite. i dont have an ETA yet for when the fix will be released.
t
Hmm, got it. 
gt track --parent <parent>
is not an option since this happens in automated scripts and the parent isn’t necessarily known.
gt get
with no PR number is always going to be cached locally, right? So that check doesn’t quite make sense.
I suppose unless I checked out a remote branch with 
git
instead of `gt`…
p
that was going to be my next question, if you used 
git
or 
gt
. since i just started at graphite, my muscle memory has been doing 
git
instead of 
gt
t
I typically do 
gt
for everything when possible, but some of my scripts do 
git
for worktree management before handing off to 
gt
, which is likely why I keep running into this
👀 1
Regardless, I would expect 
--force
to have consistent behavior for 
gt get 1234 --force
and 
gt get --force
when already on the branch for PR 1234
👍 1
2 Views
Open in Slack
PreviousNext
Powered by