Felix
07/16/2025, 3:21 PMgt sync - and switched to a different branch. Then tried to switch back with gt co BRANCH - told me couldn't find the branch locally (whcih is wierd in the first place) - then I used gt get BRANCH to get it (that worked) - another gt sync is also running fine. But I did a linting change on a single file now. run gt modify (worked fine) but gt submit fails with a pre-submit 500 errorPylon
07/16/2025, 3:21 PMgt feedback --with-debug-context <any message>Felix
07/16/2025, 3:22 PMFelix
07/16/2025, 3:22 PMFelix
07/16/2025, 3:32 PMgt get for the branch. It is displayed in graphite like this:Felix
07/16/2025, 3:33 PMPylon
07/16/2025, 3:36 PMFelix
07/16/2025, 3:39 PMFelix
07/16/2025, 3:40 PMFelix
07/17/2025, 10:09 AMPylon
07/17/2025, 1:42 PMFelix
07/17/2025, 5:39 PMgit push but after 1 or 2 prs in teh stack the pop up againPylon
07/17/2025, 6:44 PMgt feedback --with-debug-context <any message> to share logs and info about your particular gt CLI with us. We may be able to find an additional message or request ID to investigate further on our endFelix
07/17/2025, 6:50 PMFelix
07/18/2025, 10:38 AMFelix
07/18/2025, 10:45 AMgit pull then git push to get it back on track. It seems this happens when conflicts arise, but for some reason they are not tracked on gt syncPylon
07/18/2025, 1:42 PMgt feedback but it just contained the text message and no logs. Was it run with the -with-debug-context flag? That's necessary to get those to usFelix
07/18/2025, 2:47 PMFelix
07/18/2025, 2:47 PMFelix
07/18/2025, 2:51 PMFelix
07/18/2025, 2:54 PMresolve conflictgit add ... (files) git commit gt restack
resolve conflict AGAIN in gtgt continue gt submit Really annoying. Then tried to submit feedback again (so you have after picture) - but ran into a 500 error from gt feedback as well. (tried multiple times) - hard to justify this for prod workload
Pylon
07/18/2025, 2:56 PMFelix
07/18/2025, 2:57 PMFelix
07/18/2025, 2:58 PMPylon
07/18/2025, 3:02 PMgt and intend to roll out in the near future. Here's some additional guidance, which we'll be extending the existing stack collaboration doc with:
1. Don’t make meaningful changes (restacking is generally ok) to to PRs that you didn’t create.
a. Calling gt sync before gt submit is one way to guard against this.
1. It follows that if you see a merge conflict unrelated to your changes, wait for the author of those changes resolve them first, since they have more context. If you want to resolve them yourself, then let them know.
2. Communicate if you are going to make changes that could affect someone else.
3. Only one person should work on a branch at a time.Felix
07/18/2025, 3:36 PMPylon
07/18/2025, 4:11 PMFelix
07/18/2025, 7:17 PMFelix
07/18/2025, 7:19 PMPylon
07/18/2025, 7:21 PMFelix
07/18/2025, 7:24 PMFelix
07/18/2025, 7:29 PMFelix
07/18/2025, 7:29 PMgt repair would helpFelix
07/18/2025, 7:29 PMPylon
07/18/2025, 7:33 PMgt sync are you alerted to a conflict? (That should automatically restack all branches that can be without conflicts)Pylon
07/18/2025, 7:34 PMFelix
07/18/2025, 7:35 PMFelix
07/18/2025, 7:36 PMFelix
07/18/2025, 7:36 PMFelix
07/18/2025, 7:37 PMFelix
07/19/2025, 9:35 AMPylon
07/21/2025, 2:06 PMFelix
07/22/2025, 4:56 PM