This may be the same problem as with go fetch accessing a repo on the same gitea -- the git token issued to a CI job is only valid for the host repo. To clone another repo on the same gitea will need a similar solution to the one we used for go recently.
This may be the same problem as with go fetch accessing a repo on the same gitea -- the git token issued to a CI job is only valid for the host repo. To clone another repo on the same gitea will need a similar solution to the one we used for go recently.
I think all you need to do is add the `token` to the appropriate `actions/checkout` step:
```
- name: "Clone system-tests"
uses: actions/checkout@v3
with:
repository: cerc-io/system-tests
ref: main
path: ./system-tests
token: ${{ secrets.CICD_REPO_TOKEN }}
```
> I think all you need to do is add the `token` to the appropriate `actions/checkout` step:
>
> ```
> - name: "Clone system-tests"
> uses: actions/checkout@v3
> with:
> repository: cerc-io/system-tests
> ref: main
> path: ./system-tests
> token: ${{ secrets.CICD_REPO_TOKEN }}
> ```
Yep trying this now
Ah, this is because system-tests is a private repo (checking out cerc-io/plugeth and stack-orchestrator succeeds in the same job, which threw me off).
Ah, this is because `system-tests` is a private repo (checking out `cerc-io/plugeth` and stack-orchestrator succeeds in the same job, which threw me off).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Integration tests are failing due a problem with the basic auth headers.
See https://git.vdb.to/cerc-io/plugeth-statediff/actions/runs/72/jobs/1
This may be the same problem as with go fetch accessing a repo on the same gitea -- the git token issued to a CI job is only valid for the host repo. To clone another repo on the same gitea will need a similar solution to the one we used for go recently.
I think all you need to do is add the
tokento the appropriateactions/checkoutstep:Yep trying this now
Ah, this is because
system-testsis a private repo (checking outcerc-io/plugethand stack-orchestrator succeeds in the same job, which threw me off).Fixed in #10