looks like with the new version with `gt get` all ...
# how-do-i
n
looks like with the new version with
gt get
all remote branches are retrieved in "frozen" mode and not automatically restacked. Is there hopefully a global setting to have old behavior, i.e.
gt get
should not freeze and should try to restack everything
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
Thanks for flagging — taking a look!
n
image.png
p
Ah! Upon further inspection, this was intentional. We wanted
gt get
to default to the safest option, which is to put the branch in frozen mode. You can opt-out of this behavior by passing
-U
or
--unfrozen
when running
gt get
or by running
gt unfreeze
afterwards ✨
n
okay ☹️ wasn't that the difference between gt co and gt get? now they're both doing the "safest option" — not sure what's the benefit of them having the same behavior. IMO not restacking is NOT the safest if i'm doing deployment, it's quite the opposite. being push engineer i always want gt get to restack
p
Thanks for asking! 
gt co
only works with branches that already exist locally — it switches between existing branches.
gt get
does a lot of different things depending on how it is run. It's main purpose is to "get" remote changes for a branch and reconcile them locally. In most situations,
gt get
will continue to work as it has previously. Freezing only comes into play when
gt get
is pulling down a branch that is NOT already available locally. We assume in most cases, if a user is getting a branch they do not already have locally, then it is likely someone else's branch and edits to it might disrupt that user. If this is not the case and the user wants to make edits to that branch, they just need to add a new flag when running
gt get
.
n
got it thanks for explaining
👍 1