This message was deleted.
# how-do-i
s
This message was deleted.
b
Copy code
ERROR: Failed to submit PR for 03-21-Update_approval_emails_to_include_link_to_fee_schedule: Graphite encountered a 404 Not Found error when trying to submit your PR to GitHub.
This is likely either some issue with the inferred owner/name of your repo or an authentication problem.
1. Check `gt repo owner` and `gt repo name` (you can override these with the --set option for either command).
2. Check if you can see this repo in the Graphite web dashboard -- if not you may need to reauthenticate.
3. If you've already authenticated Graphite with your GitHub account via OAuth (default) and provided it with access to the current repo, GitHub recommends creating and adding a Personal Access Token, which gives Graphite the necessary permissions to submit PRs on your behalf.
(See "Using a GitHub Personal Access Token" in our documentation here: <https://docs.graphite.dev/getting-started/privacy-and-security#using-a-github-personal-access-token>)
Still not working? Don't hesitate to reach out on our Community Slack server.
p
Hi @Biniyam Asnake! Sorry you're running into this - @Emily Wu, could this be related to sync time for Graphite repos (re: not seeing the repo on the dashboard)? shouldn't be affecting CLI though right
b
@Pranathi Peri What is the right step to add the repo to my company’s graphite account?
p
What I'm referring to here is the sync time to show PRs in your repository in the Graphite dashboard after you've selected the repo during the onboarding - still don't think you should be seeing this error on the CLI though
b
after you’ve selected the repo during the onboarding
We didn’t do this. We have been on graphite for a couple months and this repo has only been introduced recently. My question is to how to add a new repo into existing graphite instance/account?
p
You've tried re-authenticating your GitHub account, right?
b
Yes I’ve ran this command
gt auth --token <your_cli_auth_token>
e
👀 From the error message, it looks like an error when we try to hit the Github API so I think it's probably unrelated to sync. Seeing if I can find any logs that could be helpful