Typically, to authenticate with github, we need to run this command in our CI environment:

git config --global url."https://${GITHUB_ACTOR}:${GITHUB_TOKEN}@github.com".insteadOf "<https://github.com>"

furthermore, we usually set:

export GOPRIVATE=<http://github.com/stedi|github.com/stedi>

In order for go mod to download private repos.

however, given all of the above info, just running

go build ./...

seems to download the modules successfully, but

./pants check ::

does not.

› ./pants lint ::
18:03:30.30 [ERROR] 1 Exception encountered:

  ProcessExecutionFailure: Process 'Download Go module <http://github.com/stedi/go-lib-auth@v1.1.3|github.com/stedi/go-lib-auth@v1.1.3>.' failed with exit code 1.
stdout:
{
	"Path": "<http://github.com/stedi/go-lib-auth|github.com/stedi/go-lib-auth>",
	"Version": "v1.1.3",
	"Error": "<http://github.com/stedi/go-lib-auth@v1.1.3|github.com/stedi/go-lib-auth@v1.1.3>: invalid version: git ls-remote -q origin in /private/var/folders/3r/76rkfbyd62xc745g5q302kmw0000gp/T/process-execution968cuF/gopath/pkg/mod/cache/vcs/9937a758f3283202f2e4e0efdaf91a97db92f7904132e022913acebe03b6494a: exit status 128:\n\tfatal: could not read Username for '<https://github.com>': terminal prompts disabled\nConfirm the import path was entered correctly.\nIf this is a private repository, see <https://golang.org/doc/faq#git_https> for additional information."
}

Of course, the docs that point to https://golang.org/doc/faq#git_https just reiterate that one needs to configure git to authenticate using https.

Also private repositories is not something we currently have tests for. So it might or might not work even with the environment configured correctly.

or even at https://www.pantsbuild.org/docs/go

After a lot of tinkering, I am unable to debug why this isn’t working - go is still giving me the git error above. I’ve tried adding

subprocess_env_vars

to pants.toml, but I’m not entirely sure this is the problem, because the ~/.gitconfig doesn’t contain any environment variables. So I guess my question is, is the git config from

$HOME/.gitconfig

even being used inside the pants sandbox? Another problem I’m running into is that I’m unable to reproduce the failure on my local machine, even after scrubbing my gitconfig, and github environment variables. I’m kind of curious why I can’t get the two to behave the same in the different environments. I’ve tried running it with

--no-pantsd

and

--no-local-cache

, but it still succeeds locally. Any help would be appreciated.

it sounds like Pants will need to add proper support for

GOPRIVATE

in order for private repos to work.

If so, the fix should be relatively confined to just the Pants rules that download module sources.

and yes - as far as I know those are the only requirements for accessing private modules

yeah, I am more just rhetorically trying to think out a potential solution in this thread