Make sure there is at least one file in it (even just the README.md)
ssh-keygen -t rsa -C "[email protected]"
or even better:
ssh-keygen -t rsa -b 4096 -C "[email protected]"
It also possible to use ed25519. There are pros and cons, but personally I've had some issues and that is the reason I've chosen to stick to 4096 rsa for now.
macOS:
pbcopy < ~/.ssh/id_rsa.pub
GNU/Linux (requires the xclip package):
xclip -sel clip < ~/.ssh/id_rsa.pub
Windows Command Line:
type %userprofile%\.ssh\id_rsa.pub | clip
Git Bash on Windows / Windows PowerShell:
cat ~/.ssh/id_rsa.pub | clip
or ofcourse copy it via your favorite editor, cat, or whatever suits your needs :)
Copy the contents of the to your SSH keys to your GitHub account settings (https://github.com/settings/keys).
ssh -T [email protected]
Change directory into the local clone of your repository (if you're not already there) and run:
git remote set-url origin [email protected]:username/your-repository.git
Now try editing a file (try the README) and then do:
git add -A
git commit -am "Update README.md"
git push
Add the key to the ssh-agent
ssh-add ~/.ssh/id_rsa
You should not be asked for a username or password. If it works, your SSH key is correctly configured.