Radosław Szalski
06/16/2025, 4:07 PMgt get <newest_branch_in_their_stack> results in Graphite telling me all of those branches have diverged and requiring me to update my colleague’s code if I do gt submit . I don’t understand where this divergence has come from because I just do gt sync followed by the above gt get. Screenshots and details in the thread.Pylon
06/16/2025, 4:07 PMgt feedback --with-debug-context <any message>Radosław Szalski
06/16/2025, 4:09 PMdevRadosław Szalski
06/16/2025, 4:10 PMRadosław Szalski
06/16/2025, 4:10 PMgt getRadosław Szalski
06/16/2025, 4:11 PMRadosław Szalski
06/16/2025, 4:11 PM1.6.4Pylon
06/16/2025, 4:12 PMgt?Radosław Szalski
06/16/2025, 4:12 PMRadosław Szalski
06/16/2025, 4:13 PMRadosław Szalski
06/16/2025, 4:22 PMgt get & gt sync after/before the checkout, and also making sure the local branches were fully deleted before doing gt getPylon
06/16/2025, 9:16 PMgt get the remote version of the stack was pulled in locally restacked onto the latest dev branch. (In the image you provided, you can see that happen after Restacking branches…
This means the local branches will indeed be based on a later version of dev than the remote branches, which means there are updates locally that need to be submitted. This also explains why you receive the message about branches having diverged.
If you don't want this behavior, you can use the --no-restack option with gt get to avoid it.Radosław Szalski
06/17/2025, 7:25 AMdev and submits that, if I then do gt sync all should be good, because bot their and my stacks would be based on the same dev version?