338

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

[email protected]: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?

corazza
  • 31,222
  • 37
  • 115
  • 186
nikhil
  • 8,925
  • 21
  • 62
  • 102
  • I think @MoOx's answer is probably most consistent with what you are seeking. The `insteadOf` trick has been around since at least 2012. Also see [How to convert `git:` urls to `http:` urls](https://stackoverflow.com/q/1722807/608639). – jww Nov 16 '17 at 21:02

9 Answers9

441

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 [email protected]: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 = [email protected]:nikhilbhardwaj/abc.git

A shortcut is to use the set-url command:

$ git remote set-url origin [email protected]:nikhilbhardwaj/abc.git

More information about the SSH-HTTPS switch

Community
  • 1
  • 1
David Cain
  • 16,484
  • 14
  • 65
  • 75
  • Thanks, I didn't know about them making smart https the default. – nikhil Jun 26 '12 at 09:29
  • 9
    This may be good for Windows users, but on Linux it was quite a step backwards: ssh always worked, and the new password caching for Smart HTTPS works only on Windows. Theres a note on *"Where's the Mac version?"* but not a **single** word for linux users. – MestreLion Sep 14 '12 at 13:13
  • I should add that, this method does not interfere with github's mac client at all. Change it and you can both use command line and gui version(github's client) of git without a problem. – Kemal Dağ Oct 11 '13 at 08:39
  • 1
    Now that GitHub is deprecating password access ([see here](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/)), it seems like this answer needs to be part of their official documentation somewhere. Is it already there? – Matt Moehr Jan 29 '21 at 20:21
  • For anyone whom this didn't work check your global git config at ~/.gitconfig. I had an insteadOf url command forcing https access. – Declan McKenna May 15 '23 at 10:55
329
  • GitHub

    git config --global url.ssh://[email protected]/.insteadOf https://github.com/
    
  • BitBucket

    git config --global url.ssh://[email protected]/.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.

corazza
  • 31,222
  • 37
  • 115
  • 186
Trevor Austin
  • 3,315
  • 1
  • 11
  • 3
120

The response provided by Trevor is correct.

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

# Enforce SSH
[url "ssh://[email protected]/"]
  insteadOf = https://github.com/
[url "ssh://[email protected]/"]
  insteadOf = https://gitlab.com/
[url "ssh://[email protected]/"]
  insteadOf = https://bitbucket.org/
Community
  • 1
  • 1
MoOx
  • 8,423
  • 5
  • 40
  • 39
10

You need to clone in ssh not in https.

$ ssh-keygen -t ed25519 -C "[email protected]"

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

If you need to have separate keys for different hosts, you can use this script:

#!/usr/bin/env bash

if [ $# -lt 2 ]; then
  echo "Provide email and hostname"
  exit 1
fi

email="$1"
hostname="$2"
keypath="$HOME/.ssh/${hostname}_rsa"
ssh-keygen -t ed25519 -C $email -f $keypath

if [ ! $? -eq 0 ]; then
  echo "Error when running ssh-keygen"
  exit 1
fi

exit 0
cat >> $HOME/.ssh/config <<EOF
Host $hostname
        User git
        IdentitiesOnly yes
        IdentityFile $keypath
EOF

and run it like

bash generate_ssh.sh [email protected] github.com

Change your remote url

git remote set-url origin [email protected]:user/foo.git

(or just edit .git/config)

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

Check connection

ssh -T [email protected]
Matt Bussing
  • 556
  • 6
  • 10
rofrol
  • 14,438
  • 7
  • 79
  • 77
  • This was handy for me except I had to change `Hostname $hostname *.$hostname` to `Hostname $hostname` for it to work. – silleknarf Mar 08 '22 at 20:11
5

SSH File

~/.ssh/config file
Host *
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null
    LogLevel QUIET
    ConnectTimeout=10
Host github.com
        User git
        AddKeystoAgent yes
        UseKeychain yes
        Identityfile ~/github_rsa

Edit reponame/.git/config

[remote "origin"]
        url = [email protected]:username/repo.git
bhargav joshi
  • 329
  • 3
  • 6
3

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.

Mike Lyons
  • 1,748
  • 2
  • 20
  • 33
2

FYI - I'm using this due to github no longer allowing ssh:

[url "[email protected]:"]
    insteadOf = https://github.com/
[url "[email protected]:"]
    insteadOf = https://gist.github.com/
Devin Rhode
  • 23,026
  • 8
  • 58
  • 72
-1

While the other answers here directly answer the titular question (in a way that I didn't know was possible! TIL something new about git!) about automagically turning https based remotes into git+ssh ones, the "normal" way to do this "right" from the start is to not give git the https url.

GitHub (along with other popular git hosting services) always has a little button that lets you get the URL that git should clone. You just need to click the small "SSH" button:

Example getting the SSH url of an existing project

Alternatively for a new project

Example getting the SSH url of an new project

Once you select the "SSH" option, GitHub (and others) will remember (as long as you're logged in) and make it the default in the future.

Cameron Tacklind
  • 5,764
  • 1
  • 36
  • 45
-1

If you are using Gitlab

git remote -v

you might see something like

https://gitlab.king.com/knight/squire.git 

just replace king, knight , squire with your own thing. knight/squire is just the way our project has different directories then you can go

git remote set-url origin ssh://[email protected]/knight/squire.git

git pull, or whatever and enjoy your genius

candyline
  • 788
  • 8
  • 17