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
@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