git - go get results in 'terminal prompts disabled' error for github private repo

ID : 10425

viewed : 26

Tags : gitgogit

Top 5 Answer for git - go get results in 'terminal prompts disabled' error for github private repo

vote vote


I found this extremely helpful, and it solved my problem. This command will allow your 2FA to do its thing (and save you the trouble of entering your username and password):

git config --global --add url."".insteadOf "" 


If you're not using 2FA, you can still use SSH and this will work.

Edit: added the --add flag as suggested by slatunje.

vote vote


go get disables the "terminal prompt" by default. This can be changed by setting an environment variable of git:

vote vote


It complains because it needs to use ssh instead of https but your git is still configured with https. so basically as others mentioned previously you need to either enable prompts or to configure git to use ssh instead of https. a simple way to do this by running the following:

git config --global --add url."".insteadOf "" 

or if you already use ssh with git in your machine, you can safely edit ~/.gitconfig and add the following line at the very bottom

Note: This covers all SVC, source version control, that depends on what you exactly use, github, gitlab, bitbucket)

# Enforce SSH [url "ssh://"]   insteadOf = [url "ssh://"]         insteadOf = [url "ssh://"]   insteadOf = 
  • If you want to keep password pompts disabled, you need to cache password. For more information on how to cache your github password on mac, windows or linux, please visit this page.

  • For more information on how to add ssh to your github account, please visit this page.

Also, more importantly, if this is a private repository for a company or for your self, you may need to skip using proxy or checksum database for such repos to avoid exposing them publicly.

To do this, you need to set GOPRIVATE environment variable that controls which modules the go command considers to be private (not available publicly) and should therefore NOT use the proxy or checksum database.

The variable is a comma-separated list of patterns (same syntax of Go's path.Match) of module path prefixes. For example,

export GOPRIVATE=*,* 


go env -w* 
  • For more information on how to solve private packages/modules checksum validation issues, please read this article.
  • For more information about go 13 modules and new enhancements, please check out Go 1.13 Modules Release notes.

One last thing not to forget to mention, you can still configure go get to authenticate and fetch over https, all you need to do is to add the following line to $HOME/.netrc

machine login USERNAME password APIKEY 
  • For GitHub accounts, the password can be a personal access tokens.
  • For more information on how to do this, please check Go FAQ page.

I hope this helps the community and saves others' time to solve described issues quickly. please feel free to leave a comment in case you want more support or help.

vote vote


1st -- go get will refuse to authenticate on the command line. So you need to cache the credentials in git. Because I use osx I can use osxkeychain credential helper.

2nd For me, I have 2FA enabled and thus could not use my password to auth. Instead I had to generate a personal access token to use in place of the password.

  1. setup osxkeychain credential helper
  2. If using TFA instead of using your password, generate a personal access token with repo scope
  3. git clone a private repo just to make it cache the password git clone and used your username for username and the generated personal access token for password.
  4. Removed the just cloned repo and retest to ensure creds were cached -- git clone and this time wasnt asked for creds.

    1. go get will work with any repos that the personal access token can access. You may have to repeat the steps with other accounts / tokens as permissions vary.
vote vote


If you just want go get to work real fast, and move along with your work...


$ export GIT_TERMINAL_PROMPT=1 $ go get [whatever] 

It will now prompt you for a user/pass for the rest of your shell session. Put this in your .profile or setup git as above for a more permanent solution.

Top 3 video Explaining git - go get results in 'terminal prompts disabled' error for github private repo