Codespaces didn't have my ssh keys and wasn't authorized to reach https github #9571
Replies: 3 comments 3 replies
-
Have you enabled access to the repository you're trying to push to (or all your repositories)? |
Beta Was this translation helpful? Give feedback.
-
After rereading your comment No I had not set that, it's a very scary option based on the description alone. All codespaces can access my repositories? |
Beta Was this translation helpful? Give feedback.
-
You can also add your private ssh key linked to your github account, onto your codespace. I just did that and was able to push to my fork. You also have to change the git origin with |
Beta Was this translation helpful? Give feedback.
-
I created a personal codespace from a github repository I didn't own.
I wrote code.
I tried to push with the sync button. VSCode helpfully tells me I don't have permission to push to x/y, asks if I want to fork the repository?
I click yes.
It tells me I don't have permission to push to krainboltgreene/y, would I like to fork it? (This will probably be an infinite loop)
Turns out my vscode doesn't have my ssh keys, didn't have my dotfiles, and the https url VScode helpfully set as my
origin
repository just 403's without any input.Beta Was this translation helpful? Give feedback.
All reactions