Open basz opened 2 years ago
I wonder if we could use actions/checkout
as child action :thinking:
Doing the cloning ourselves is both inefficient (github is smarter about it), and unsafe (we may leak secrets during crashes).
@basz meanwhile, do you know which git
command it executed, precisely?
My thought exactly. Just don't know how...
Looking at the output "Cloning repository" I'm guessing here and combined with GITHUB_REPOSITORY from that should be;
git clone https://github.com/plhw/lab-api-model-valueobject
.
Could it be double "
's? in that line or in the docker command? -e "$SOME_ENV"
vs -e SOME_ENV
asked because it seems GITHUB_REPOSITORY is empty...
just noting; adding a checkout step before laminas/laminas-ci-matrix-action resolves this issue. credentials are saved and laminas cn continue
- name: Checkout
uses: actions/checkout@v3
I've also found it's necessary to set fetch-depth
to zero for the matrix to be generated on a pull request to a private project.
jobs:
matrix:
name: Generate job matrix
runs-on: ubuntu-latest
outputs:
matrix: ${{ steps.matrix.outputs.matrix }}
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: '0'
- name: Gather CI configuration
id: matrix
uses: laminas/laminas-ci-matrix-action@v1
qa:
name: QA Checks
needs: [ matrix ]
runs-on: ${{ matrix.operatingSystem }}
strategy:
fail-fast: false
matrix: ${{ fromJSON(needs.matrix.outputs.matrix) }}
steps:
- name: Checkout
uses: actions/checkout@v4
- name: ${{ matrix.name }}
uses: laminas/laminas-continuous-integration-action@v1
env:
"GITHUB_TOKEN": ${{ secrets.GITHUB_TOKEN }}
with:
job: ${{ matrix.job }}
Bug Report
Summary
Initial git clone fails for private repositories
Current behavior
How to reproduce
Expected behavior
Initial checkout succeeds
Notes
Shouldn't the auth token be persisted to the local git config before it can be used by git commands? actions/checkout action seems to do that (See the Readme).