Nikola Mihajlovic
09/17/2025, 9:09 PMgt 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 everythingPylon
09/17/2025, 9:10 PMPylon
09/17/2025, 9:10 PMNikola Mihajlovic
09/17/2025, 9:11 PMPylon
09/17/2025, 9:20 PMgt 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 ✨Nikola Mihajlovic
09/17/2025, 11:01 PMPylon
09/18/2025, 2:50 PMgt 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.Nikola Mihajlovic
09/18/2025, 3:58 PM