gt branch track. Don’t worry, your current stacks are fine — existing Graphite branches with valid stack metadata will be migrated over cleanly. gt branch track is also the command to get a branch back in a valid state if its metadata ever gets corrupted by a Graphite bug or external issue.repo init flow walks you through the process of tracking some of your existing local branches when you start using the CLI in a repository.fix --regen command and replaced the fix --rebase command with a new command called restack. The restack command can be run on a branch, stack, downstack, or upstack (just like submit).restack operation, for each branch in its scope, ensures that its parent branch is actually in its git ancestry, rebasing if necessary. The new engine of the CLI ensures that only commits that are intended to be part of the branch are rebased, as well as reducing the amount of logic that needs to be run in order to check validation state. The end result is the same invariant that prior versions of the CLI enforced — that a PR can only be created/updated when its head branch is correctly situated on its base.regen version of fix? Quick reminder, regen was meant to allow for easily constructing Graphite stacks from “stacks” of git branches that Graphite previously did not know about, or whose Graphite. Now that branches need to be explicitly tracked with gt branch track, the new way to do this is to track each branch, specifying its parent as you go!git commandsgit — we hope that the new model of restacking allows us to do this a little better!restack to fix your stack before running stack submit.