Hello! Recently on of my repos started showing thi...
# report-bugs
a
Hello! Recently on of my repos started showing this message whenever I try to push:
Copy code
āÆ gt submit
šŸ„ž Validating that this Graphite stack is ready to submit...
Trunk branch (main) is behind its upstream branch. Please run gt sync to update.
Failure to update could result in incorrect metadata being used to submit PRs.
āœ” Continue with this submit operation? … yes
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
Sent debug context via CLI.
Notably it only happens on one repo.
p
hey Anton, the team is working on improving this warning in the next release, but in the meantime to avert this prompt the
gt submit
command can be used with the
--ignore-out-of-sync-trunk
flag. You're also able to use
gt aliases
to set the
submit
command to always run with that particular flag enabled.
a
Thanks! What does it mean to have an out-of-sync trunk?
p
I think it's when your local version of trunk is behind the state of the remote version
a
Ah, I ran
gt submit --debug
and saw this:
Copy code
2025-09-05T22:20:18.216Z: Finished getUpstreamBranch (72624): git rev-parse --abbrev-ref --symbolic-full-name main@{u}
{
  "code": 128,
  "signal": null,
  "stdout": "",
  "stderr": "fatal: no upstream configured for branch 'main'\n"
}
My
main
branch wasn't pointing to the upstream
origin/main
.
git branch --set-upstream-to=origin/main main
fixed it.
šŸ‘ 1
n
Weirdly I'm getting the same issue - this didn't fix it though
p
improvements to this prompt will be included in our
1.7.0
release out next week (available in beta)
n
How can I get on the beta?
I use brew to install rn
Ah found it, thanks
@Gareth Brickman same issue šŸ˜•
p
Please run
gt feedback --with-debug-context <any message>
to share logs and info about your particular
gt
CLI with us.
šŸ‘ 1
hey Nick, we see that you did perform a submit in which
main
and
origin/main
were aligned and we did not print the warning. But after running a number of other commands the next time you ran
submit
main
was pointing at the same commit as previously, but
origin/main
had moved to another commit.
n
What does that mean? This is the command I'm running
gt modify --all && gt submit --stack
Also what is the new gt freeze/unfreeze?
p
gotcha, I think try syncing before running the submit. For
gt freeze/unfreeze
, we have docs here