Isn't my GitHub SSH key supposed to free me from writing credentials every time?

A colleague has told me to make a ssh key and import it in GitHub. Before I did that, I was getting “access denied” errors (or similar) when npm checked out dependencies from GitHub, but now it works fine. However, I still need to enter my credentials every time I push to the remote. Isn’t the SSH key supposed to free me from that?

(Note: The passphrase of my ssh key is empty)

  • eclipse error cloning git repository from tfs authentication not supported
  • Visual Studio 2013 and Github account authentication not working
  • 401 Unauthorized SVN - Login Repository
  • Pull from github without authentication every time
  • Authentication from external tools with TFS Git repository
  • How do I check whether I have access to a repository without cloning?
  • Edit: I just the GitHub docs on this and it seems that the problem is that I’ve checked out via HTTPS instead of SSH. Is that so?

  • How do you delete a remote annotated tag?
  • Repull changes in git
  • Add a git merge driver to the repository?
  • how to know the depth of a git's shallow clone?
  • Diff only changed parts of lines
  • how to get git to ignore a file (wild card files)
  • One Solution collect form web for “Isn't my GitHub SSH key supposed to free me from writing credentials every time?”

    Use git remote -v to show your remotes. If they start with “HTTPS”, then it isn’t using SSH. Use git remote set-url to change it to the SSH location.

    Git Baby is a git and github fan, let's start git clone.