.netrc file so you can push/pull to https git repos without entering your creds all the time

gistfile1.txt

machine github.com
login technoweenie
password SECRET

machine api.github.com
login technoweenie
password SECRET

Stick this in ~/.netrc with chmod 600 or something. You can curl the api as yourself with curl -n https://api.github.com/user

Stick this in ~/.netrc with chmod 600 or something. You can curl the api as yourself with curl -n https://api.github.com/user

What about per-repository login?

What about per-repository login?

@noamtm I just checked, netrc or gitcredentials aren't up to the task (the latter has an option to match on host paths, but prefix matches are missing so it's only semi-convenient). If you control the url you should put the username in the url or use host aliases, both ssh (man ssh_config) and git (git help config then /insteadof) have them; if you can't (go get or pip remote requirements), there is no convenient solution.

@noamtm I just checked, netrc or gitcredentials aren't up to the task (the latter has an option to match on host paths, but prefix matches are missing so it's only semi-convenient). If you control the url you should put the username in the url or use host aliases, both ssh (man ssh_config) and git (git help config then /insteadof) have them; if you can't (go get or pip remote requirements), there is no convenient solution.

Note about a limitation: password in .netrc file should not contain spaces, since the .netrc file is parsed against spaces, tabs and new-lines.

Note about a limitation: password in .netrc file should not contain spaces, since the .netrc file is parsed against spaces, tabs and new-lines.

Thanks man! Exactly what I needed

Thanks man! Exactly what I needed

Any way to store password here not in plain text.
It's too risky to store in plaintext

Any way to store password here not in plain text.
It's too risky to store in plaintext

@kprikshit http://stackoverflow.com/a/18362082/1044366

@kprikshit http://stackoverflow.com/a/18362082/1044366

github supports the access token instead of password: https://help.github.com/articles/creating-an-access-token-for-command-line-use/

github supports the access token instead of password: https://help.github.com/articles/creating-an-access-token-for-command-line-use/

With respect, I would definitely recommend authenticating to github using ssh with decryption key instead of the .netrc method, as it's insecure: https://help.github.com/articles/generating-an-ssh-key/

With respect, I would definitely recommend authenticating to github using ssh with decryption key instead of the .netrc method, as it's insecure: https://help.github.com/articles/generating-an-ssh-key/

@rhiannon that's all good until you are somewhere that blocks 22 outbound.

@rhiannon that's all good until you are somewhere that blocks 22 outbound.

@andrewspiers I thought that you can alternatively use port 443 outbound for SSH traffic... Or am I confused with bitbucket...?

@andrewspiers I thought that you can alternatively use port 443 outbound for SSH traffic... Or am I confused with bitbucket...?

@andrewspiers https://help.github.com/articles/using-ssh-over-the-https-port/#enabling-ssh-connections-over-https

@andrewspiers https://help.github.com/articles/using-ssh-over-the-https-port/#enabling-ssh-connections-over-https

Thanks! Exactly what I needed

Thanks! Exactly what I needed

Is it possible to add a default editor within this file?
I am tring to use git pull-request and keep getting this error:
$EDITOR is unset, you will not be able to edit the pull-request message

Is it possible to add a default editor within this file?
I am tring to use git pull-request and keep getting this error:
$EDITOR is unset, you will not be able to edit the pull-request message

Hi, what about git-credentials and git-credentials-store ?

Hi, what about git-credentials and git-credentials-store ?