When I am writing a stack, I frequently use `gt up...
# how-do-i
z
When I am writing a stack, I frequently use `gt up`/`gt down`. Today for the first time I checked out a branch to review, and I noticed that `gt up`/`gt down` do NOT move up and down a stack that someone else has written/stacked/submitted. I tried
gt get
,
gt sync
to try to "pull" the stacking metadata. Is there any way to locally inherit remote stacking order? Thank you!
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
Hey Zach, curious. This should definitely work, thought it might have been a frozen branch issue but that too worked for me. Few questions: • What
gt --version
are you on? • how did you check out your colleagues branch?
gt get <branch>
? • does
gt ls
show you the stack?
Follow up here Zach, just found the log of your
gt up
failure. Seems like the branch you checked out had not yet been tracked by graphite.
gt track
should fix this.
z
Hi @Brett Bedevian I've narrowed this to what I think is a real issue. If I've checked out a branch locally,
gt get <branchname>
will ensure I can move up and downstack (`gt up`/`gt down` work properly). But
gt get
on its own does NOT result in this state! This is confusing because
gt get --help
shows this:
If no branch is provided, sync the current stack.
I think
gt get
with no branch provided should sync the required metadata for my local graphite to know which branch tracks which in the stack I'm on if there's an open PR/stack on graphite for the current branch. If there's an argument against this I'm curious what it'd be. Thanks @Brett Bedevian for the response.
p
Thanks for digging into this one. I dont have any arguement against it.