How do I get git to default to ssh and not https f

问题:

These days when I create a new repository on GitHub on the setup page I get:

git remote add origin https://github.com/nikhilbhardwaj/abc.git
git push -u origin master

And whenever I have to push a commit I need to enter my GitHub username and password.

I can manually change that to

[e-mail]:nikhilbhardwaj/abc.git

in the .git/config. I find this quite irritating - is there some way I can configure git to use SSH by default?

回答1:

Set up a repository's origin branch to be SSH

The GitHub repository setup page is just a suggested list of commands (and GitHub now suggests using the HTTPS protocol). Unless you have administrative access to GitHub's site, I don't know of any way to change their suggested commands.

If you'd rather use the SSH protocol, simply add a remote branch like so (i.e. use this command in place of GitHub's suggested command). To modify an existing branch, see the next section.

$ git remote add origin [e-mail]:nikhilbhardwaj/abc.git

---

Modify a pre-existing repository

As you already know, to switch a pre-existing repository to use SSH instead of HTTPS, you can change the remote url within your .git/config file.

[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    -url = https://github.com/nikhilbhardwaj/abc.git
    +url = [e-mail]:nikhilbhardwaj/abc.git

A shortcut is to use the set-url command:

$ git remote set-url origin [e-mail]:nikhilbhardwaj/abc.git

---

More information about the SSH-HTTPS switch

• "Why is Git always asking for my password?" - GitHub help page.
• GitHub's switch to Smart HTTP - relevant StackOverflow question
• Credential Caching for Wrist-Friendly Git Usage - GitHub blog post about HTTPS, and how to avoid re-entering your password

回答2:

• GitHub

  git config --global url.ssh://[e-mail]/.insteadOf https://github.com/
  

• BitBucket

  git config --global url.ssh://[e-mail]/.insteadOf https://bitbucket.org/
  

That tells git to always use SSH instead of HTTPS when connecting to GitHub/BitBucket, so you'll authenticate by certificate by default, instead of being prompted for a password.

回答3:

The response provided by Trevor is correct.

But here is what you can directly add in your .gitconfig:

# Enforce SSH
[url "ssh://[e-mail]/"]
  insteadOf = https://github.com/
[url "ssh://[e-mail]/"]
  insteadOf = https://gitlab.com/
[url "ssh://[e-mail]/"]
  insteadOf = https://bitbucket.org/

回答4:

If you want many keys for different hosts, do this:

Create a script

#!/usr/bin/env bash
email="$1"
hostname="$2"
hostalias="$hostname"
keypath="$HOME/.ssh/${hostname}_rsa"
ssh-keygen -t rsa -C $email -f $keypath
if [ $? -eq 0 ]; then
cat >> ~/.ssh/config <<EOF
Host $hostalias
        Hostname $hostname
        User git
    IdentitiesOnly yes
        IdentityFile $keypath
EOF
fi

and run it like

sh script.sh [e-mail] github.com

Change your remote url

git remote set-url origin [e-mail]:user/foo.git

Add content of ~/.ssh/github.com_rsa.pub to your ssh keys on github.com

Check connection

ssh -T [e-mail]

回答5:

You may have accidentally cloned the repository in https instead of ssh. I've made this mistake numerous times on github. Make sure that you copy the ssh link in the first place when cloning, instead of the https link.