12
─[$] cat ~/.gitconfig

[user]
    name = Shirish Agarwal
    email = xxxx@xxxx.xxx
[core]
    editor = leafpad
    excludesfiles = /home/shirish/.gitignore
    gitproxy = \"ssh\" for gitorious.org
[merge]
    tool = meld
[push]
    default = simple
[color]
    ui = true
    status = auto
    branch = auto

Now I want to put my git credentials for github, gitlab and gitorious so each time I do not have to lookup the credentials on the browser. How can this be done so it's automated ?

I am running zsh

  • What kind of credentials are you using - typically these days you set up ssh? – icarus Jan 8 '17 at 5:57
  • umm... this was from sometime ago, so maybe ssh isn't setup, I'm not sure. – shirish Jan 8 '17 at 8:12
  • This is not Unix/Linux specific, should have sent it to SuperUser or SO... but whatever :) – Ondra Žižka Sep 3 '18 at 19:41
14

Using SSH

The common approach for handling git authentication is to delegate it to SSH. Typically you set your SSH public key in the remote repository (e.g. on GitHub), and then you use that whenever you need to authenticate. You can use a key agent of course, either handled by your desktop environment or manually with ssh-agent and ssh-add.

To avoid having to specify the username, you can configure that in SSH too, in ~/.ssh/config; for example I have

Host git.opendaylight.org
  User skitt

and then I can clone using

git clone ssh://git.opendaylight.org:29418/aaa

(note the absence of a username there).

Using gitcredentials

If the SSH approach doesn't apply (e.g. you're using a repository accessed over HTTPS), git does have its own way of handling credentials, using gitcredentials (and typically git-credential-store). You specify your username using

git config credential.${remote}.username yourusername

and the credential helper using

git config credential.helper store

(specify --global if you want to use this setup everywhere).

Then the first time you access a repository, git will ask for your password, and it will be stored (by default in ~/.git-credentials). Subsequent accesses to the repository will use the stored password instead of asking you.

  • 1
    can you elaborate a bit about credential.${remote} and credential.helper. Is there some documentation you could point out as this is the first time I am reading about it. – shirish Jan 8 '17 at 19:14
  • I linked to the manpages in my answer, that's the documentation. ${remote} is the protocol and hostname part of the URI you want to clone, helper points to a helper program. – Stephen Kitt Jan 8 '17 at 19:22
  • 1
    There's also a chapter of Pro Git on the topic. – Stephen Kitt Jan 8 '17 at 19:24
6

For those finding this later -- I had difficulties with this and finally made it work

https / credentials.helper / Ubuntu

  1. Unset Globally:
    git config --global --unset credentials.helper
  2. Unset locally: (In each repo) git config --unset credential.helper
  3. Create credential file for each repo: (inside each repo)

    git config credential.helper 'store --file ~/.git_reponame_credentials'
    

Not saying it is the best way or the only way - but it worked for me after several frustrating hours.

  • seems to be similar to what stephen kitt shared above. – shirish May 12 '18 at 15:20
  • 1
    @shirish not really, the third point was the one I needed - option to specify where the files is located. – Mārtiņš Briedis Feb 6 at 21:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.