This message was deleted.
# how-do-i
s
This message was deleted.
b
I think you want to look at
gt branch track
r
Doesn't work.
Copy code
auto-sync ❯ g btr
Tracked branch auto-sync with parent main.
.
Copy code
auto-sync took 12s ❯ g ds submit
🥞 Validating that this Graphite stack is ready to submit...

✏️  Preparing to submit PRs for the following branches...
▸ auto-sync (Create)
✔ Title … remove ngram
✔ Body › Skip (paste commit messages)
✔ Submit › Create Draft Pull Request

📨 Pushing to remote and creating/updating PRs...
ERROR: Your Graphite auth token is invalid/expired.

Please obtain a new auth token by visiting <https://app.graphite.dev/activate>
lucky my token was invalid, otherwise that would've created a spam PR...
🫣 1
I remember running
gt branch track
right at the beginning. And that was necessary for gt to recognize my branch as a stack. But it doesn't connect with the PR that already exists on github.
ohhh the authentication was actually the problem...
IIRC, I authenticated by pasting the token from github, not the one from graphite... guess that was my mistake.
But clearly the CLI is already trying to make API requests before prompting me to create a new PR. Why doesn't it fail then and there? If these early requests fail already, it's already known that the later submission of a new PR will also fail.
Anyway, thanks for getting me on the right track.
👍 1
b
Good question about error handling. Hopefully the Graphite team will have thoughts on Monday!
p
Hey there! Thanks for the feedback - I'll bring it up with the team and let you know what they say!
Quick follow-up, the CLI eng team is aware of this and are planning on fixing soon! Again, thanks for the feedback - super helpful for us!
c
+1, just ran into this one too -- I was trying to update a PR in a repo that Graphite didn’t have access to, and it offered to create a new PR when really it probably should have given an auth error. After granting Graphite access to the repo, it started working correctly