hi. on my stack, when i run `gt sync` it says that...
# report-bugs
a
hi. on my stack, when i run
gt sync
it says that everything is up-to-date:
Copy code
āÆ 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:
Copy code
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?
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>
a
i ran
gt submit --force
and then looking at the diff in the web ui, seems like there are no changes
another context: in this stack at some point i reordered prs and then merged the first one (the one it complains about was the second one at the time)
p
hey Anton, thanks for using
gt feedback -d
to send along your CLI logs as well. Confirming we've received those on our end
šŸ‘ 1
hey Anton, this bug will be fixed in the upcoming
1.6.6
release, which is currently in Beta. In the meantime, the workaround is to submit with the `--force`​ flag.