Anton Kovalyov
06/11/2025, 6:59 PMgt sync it says that everything is up-to-date:
⯠gt sync
š² Fetching branches from remote...
Running git fetch: [========================================] 100% | Done
main is up to date.
š Syncing branches...
Branch anton-06-09-<redacted> is up to date with remote (PR #10837 v6).
Branch anton-06-09-<redacted> is up to date with remote (PR #10838 v5).
Branch anton-06-10-<redacted> is up to date with remote (PR #10848 v6).
Branch anton-06-10-<redacted> is up to date with remote (PR #10855 v3).
š„ Restacking branches...
anton-06-09-<redacted> does not need to be restacked on main.
anton-06-09-<redacted> does not need to be restacked on anton-06-09-<redacted>.
anton-06-10-<redacted> does not need to be restacked on anton-06-09-<redacted>.
anton-06-10-<redacted> does not need to be restacked on anton-06-10-<redacted>.
anton-06-11-<redacted> does not need to be restacked on anton-06-10-<redacted>.
anton-06-11-<redacted> does not need to be restacked on anton-06-11-<redacted>.
but when i try to submit new branches, it fails with this error:
ERROR: Branch anton-06-09-<redacted> has been updated remotely. Use gt get or gt sync to sync with remote before submitting (or use the --force flag to override this check).
any thoughts why this would be the case?Pylon
06/11/2025, 6:59 PMgt feedback --with-debug-context <any message>Anton Kovalyov
06/11/2025, 7:06 PMgt submit --force and then looking at the diff in the web ui, seems like there are no changesAnton Kovalyov
06/11/2025, 7:06 PMPylon
06/11/2025, 7:46 PMgt feedback -d to send along your CLI logs as well. Confirming we've received those on our endPylon
06/18/2025, 2:55 PM1.6.6 release, which is currently in Beta. In the meantime, the workaround is to submit with the `--force`ā flag.