Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
.netrc file so you can push/pull to https git repos without entering your creds all the time
machine github.com
login technoweenie
password SECRET
machine api.github.com
login technoweenie
password SECRET
@soupdiver
Copy link

soupdiver commented Jul 9, 2014

Thanks man! Exactly what I needed

@kprikshit
Copy link

kprikshit commented May 1, 2015

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

@sandeepraju
Copy link

sandeepraju commented Jul 7, 2015

@snowyu
Copy link

snowyu commented Jul 24, 2015

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

@andrewspiers
Copy link

andrewspiers commented Feb 7, 2017

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

@felipe1982
Copy link

felipe1982 commented Mar 14, 2017

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

@miradnan
Copy link

miradnan commented Mar 23, 2018

Thanks! Exactly what I needed

@LiviuLvu
Copy link

LiviuLvu commented May 19, 2018

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

@kopax
Copy link

kopax commented Oct 2, 2018

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

@coolaj86
Copy link

coolaj86 commented Jul 24, 2019

Excerpt from

The Vanilla DevOps Git Credentials & Private Packages Cheatsheet

GIT_ASKPASS

GIT_ASKPASS and SSH_ASKPASS are probably the least hacky approaches, but not as flexible as some of the others.

export GIT_ASKPASS=$HOME/.git-askpass.sh

~/.git-askpass.sh

#!/bin/bash
echo xxxxxxxx
chmod 0700 ~/.git-askpass.sh

.gitconfig

The .gitconfig approach has the advantage of being able to interchange ssh, git, and https urls and you can use granular path matching.

.gitconfig:

[url "https://api:xxxxxxxx@github.com/"]
  insteadOf = https://github.com/
[url "https://api:xxxxxxxx@github.com/"]
  insteadOf = https://api@github.com/
[url "https://api:xxxxxxxx@github.com/"]
  insteadOf = ssh://git@github.com/
[url "https://api:xxxxxxxx@github.com/"]
  insteadOf = git@github.com:

Which you can create by doing this:

git config --global url."https://api:xxx@github.com/".insteadOf "ssh://git@github.com/"
git config --global url."https://api:xxx@github.com/".insteadOf "git@github.com:"
git config --global url."https://api:xxx@github.com/".insteadOf "https://github.com/"
git config --global url."https://api:xxx@github.com/".insteadOf "https://api:github.com/"

git-credentials

This is nice because it's very granular and you can combine it with the trick above.

git config credential.helper store

~/.git-config:

[url "https://github.com/"]
  insteadOf = ssh://git@github.com/
[credential]
    helper = store

~/.git-credentials:

https://api:xxxxxxx@github.com/myorganization/

.netrc

~/.netrc:

machine github.com
login api
password xxxxxxxx

@Varriount
Copy link

Varriount commented Oct 22, 2019

For those in the future wondering why this might not work - as of Go 1.13.x, Go uses proxies when downloading packages and verifying checksums.

In order to bypass the proxies, you'll need to set the environment variables GOPROXY, GONOPROXY, GOSUMDB, GONOSUMDB to the appropriate values.

For example, from the documentation:

GOPRIVATE=*.corp.example.com
GOPROXY=proxy.example.com
GONOPROXY=none

This states:

  • Packages matching *.corp.example.com are private (and thus the proxy and checksum sites will not be used to download/verify them).
  • Use proxy.example.com as the proxy for downloading packages (though note that this does not set the checksum site).
  • Only packages matching "none" should not be proxied (so, unless you have a package called "none", all packages will be proxied). This overrides the first line/the GOPRIVATE variable.

@kleaver
Copy link

kleaver commented Jun 15, 2021

Something interesting I found while testing the .netrc with go+git+GitHub: when using a GitHub personal access token (PAT) for the password in the .netrc, the value given for login can be any arbitrary value, it doesn't need to be the username that the PAT was generated for (it does need to be set to something though).

@CarlosDomingues
Copy link

CarlosDomingues commented Feb 9, 2022

Instructions for GitLab folks, as this was one of my first results of Googling "GitLab .netrc":

machine gitlab.com
login oauth2
password <PERSONAL_ACCESS_TOKEN>

That enables:

  • Cloning repos with https
  • Accessing some private package registries with https (ex: pypi)
  • Login in GitLab's private container registry using docker login registry.gitlab.com

(of course your <PERSONAL_ACCESS_TOKEN> needs the correct capabilities)

Also, during CI:

build_job:
    script:
    - |
      echo "
      machine gitlab.com
      login gitlab-ci-token
      password $CI_JOB_TOKEN
      " > ~/.netrc
    - <stuff>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment