Update: Decided against PAT for building Go projects with private repo dependencies with GitHub actions because managing ssh keys is just so much more flexible and easy to setup—especially when storing the ssh key in Vault. Using PAT creates an implicit dependency on GitHub that unnecessarily locks the CI/CD to GitHub that need not be. Also, when I first created this zet I mistakenly read that the GH_ACCESS_TOKEN was automatically created when, in fact, it has to be created using the GH personal access token interface (as outlined in the images that I didn’t see when doing the research initially).
jobs:
run:
runs-on: ubuntu-latest
env:
GOPRIVATE: github.com/fabianMendez/privatemodule
GH_ACCESS_TOKEN: $
steps:
- uses: actions/checkout@v2
- uses: actions/setup-go@v2
with:
go-version: '1.16'
- run: git config --global url.https://$GH_ACCESS_TOKEN@github.com/.insteadOf https://github.com/
- run: go build
om/
!!! warning
DO NOT FORGET THE TRAILING SLASHES IN git config --global LINE!
But what about limited to url.ssh?