Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/website: FAQ on private git repos should mention GOPRIVATE #71797

Closed
HouzuoGuo opened this issue Feb 17, 2025 · 3 comments
Closed

x/website: FAQ on private git repos should mention GOPRIVATE #71797

HouzuoGuo opened this issue Feb 17, 2025 · 3 comments
Labels
Documentation Issues describing a change to documentation. NeedsFix The path to resolution is known, but the work has not been done. website
Milestone
Unreleased

Comments

@HouzuoGuo
Copy link

The failure message for go get to download a private repository says:

 exit status 128:
                fatal: could not read Username for 'https://github.com': terminal prompts disabled
        Confirm the import path was entered correctly.
        If this is a private repository, see https://golang.org/doc/faq#git_https for additional information.

The guidance at https://golang.org/doc/faq#git_https only mentions:

Git can be configured to authenticate over HTTPS or to use SSH in place of HTTPS. To authenticate over HTTPS, you can add a line to the $HOME/.netrc file that git consults ...

Which is insufficient, it is in fact also crucial set GOPRIVATE= environment variable to include the repository paths, or go get will be contacting proxy and sum DB and fail.

Please update golang.org/doc/faq#git_https and mention the mandatory usage of GOPRIVATE= in combination with the authentication trick there.
@gopherbot gopherbot added the Documentation Issues describing a change to documentation. label Feb 17, 2025
@seankhliao seankhliao changed the title Documentation golang.org/doc/faq#git_https: insufficient guidance re: cloning private repository x/website: FAQ on private git repos should mention GOPROVATE Feb 17, 2025
@gopherbot gopherbot added this to the Unreleased milestone Feb 17, 2025
@gabyhelp
Copy link

Related Issues

Related Code Changes

Related Documentation

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@mknyszek mknyszek changed the title x/website: FAQ on private git repos should mention GOPROVATE x/website: FAQ on private git repos should mention GOPRIVATE Feb 18, 2025
@mknyszek mknyszek added the NeedsFix The path to resolution is known, but the work has not been done. label Feb 18, 2025
@mknyszek
Copy link
Contributor

CC @matloob @samthanawalla maybe? Since GOPRIVATE IIRC is all part of the Go command. Please feel free to redirect if I'm wrong. Thanks.

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/650336 mentions this issue: _content/doc: mention GOPRIVATE in FAQ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation Issues describing a change to documentation. NeedsFix The path to resolution is known, but the work has not been done. website
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
4 participants
@HouzuoGuo @mknyszek @gopherbot @gabyhelp