[GH-ISSUE #843] Issue: checkout a different enterprise repo action fails with token error in workflow #511

Closed
opened 2026-03-01 21:44:04 +03:00 by kerem · 1 comment
Owner

Originally created by @mssanjay on GitHub (Oct 18, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/843

System information

  • Operating System: Windows
  • Architecture:
  • Apple M1:
  • Docker version:
  • Docker image used in act: ubuntu-latest
  • act version: 0.2.24

Expected behaviour

Checkout action should checkout a private repo

Actual behaviour

[ci/build] 🐳 docker exec cmd=[node /var/run/act/actions/actions-checkout@v2/dist/index.js] user=
[ci/build] Exec command '[node /var/run/act/actions/actions-checkout@v2/dist/index.js]'
[ci/build] ::save-state name=isPost::true
[ci/build] 💬 ::debug::GITHUB_WORKSPACE = '/mnt/c/Users/smelina/dev/code2/apigateway_gitactions-testing'
[ci/build] 💬 ::debug::qualified repository = 'https://git.mycompany.com/my-org/my-repo'
[ci/build] ::error::Invalid repository 'https://git.mycompany.com/my-org/my-repo'. Expected format {owner}/{repo}.
time="2021-10-17T21:57:15-04:00" level=debug msg="exit with FAILURE: 1"
[ci/build] Failure - checkoutGatewayRepo

I have a second repo that I need to checkout and perform a merge. The checkout action fails to checkout this repo.
I am able to run this workflow in our github enterprise actions but not with ACT.

Workflow and/or repository

- name: checkoutGatewayRepo
  uses: actions/checkout@v2
  with:
      repository: ${{ steps.get-gateway-repo.outputs.gatewayRepo }}
      path: konggateway
      ref: ${{ steps.extract-branch-name.outputs.branch }}
      token: ${{ secrets.RUNNER_GIT_TOKEN }}

Steps to reproduce

act output

Log
[ci/build]   🐳  docker exec cmd=[node /var/run/act/actions/actions-checkout@v2/dist/index.js] user=
[ci/build] Exec command '[node /var/run/act/actions/actions-checkout@v2/dist/index.js]'
[ci/build]   ❓  ::save-state name=isPost::true
[ci/build]   💬  ::debug::GITHUB_WORKSPACE = '/mnt/c/Users/smelina/dev/code2/apigateway_gitactions-testing'
[ci/build]   💬  ::debug::qualified repository = 'https://git.mycompany.com/my-org/my-repo'
[ci/build]   ❗  ::error::Invalid repository 'https://git.mycompany.com/my-org/my-repo'. Expected format {owner}/{repo}.
time="2021-10-17T21:57:15-04:00" level=debug msg="exit with `FAILURE`: 1"
[ci/build]   ❌  Failure - checkoutGatewayRepo
Originally created by @mssanjay on GitHub (Oct 18, 2021). Original GitHub issue: https://github.com/nektos/act/issues/843 <!-- - Make sure you are able to reproduce it on the [latest version](https://github.com/nektos/act/releases) - Search the existing issues. - Refer to [README](https://github.com/nektos/act/blob/master/README.md). --> ## System information <!-- - Operating System: < Windows | Linux | macOS | etc... > - Architecture: < x64 (64-bit) | x86 (32-bit) | arm64 (64-bit) | arm (32-bit) | etc... > - Apple M1: < yes | no > - Docker version: < output of `docker system info -f "{{.ServerVersion}}"` > - Docker image used in `act`: < can be omitted if it's included in log > - `act` version: < output of `act --version`, if you've built `act` yourself, please provide commit hash > --> - Operating System: Windows - Architecture: - Apple M1: - Docker version: - Docker image used in `act`: ubuntu-latest - `act` version: 0.2.24 ## Expected behaviour <!-- - Describe how whole process should go and finish --> Checkout action should checkout a private repo ## Actual behaviour [ci/build] 🐳 docker exec cmd=[node /var/run/act/actions/actions-checkout@v2/dist/index.js] user= [ci/build] Exec command '[node /var/run/act/actions/actions-checkout@v2/dist/index.js]' [ci/build] ❓ ::save-state name=isPost::true [ci/build] 💬 ::debug::GITHUB_WORKSPACE = '/mnt/c/Users/smelina/dev/code2/apigateway_gitactions-testing' [ci/build] 💬 ::debug::qualified repository = 'https://git.mycompany.com/my-org/my-repo' [ci/build] ❗ ::error::Invalid repository 'https://git.mycompany.com/my-org/my-repo'. Expected format {owner}/{repo}. time="2021-10-17T21:57:15-04:00" level=debug msg="exit with `FAILURE`: 1" [ci/build] ❌ Failure - checkoutGatewayRepo <!-- - Describe the issue --> I have a second repo that I need to checkout and perform a merge. The checkout action fails to checkout this repo. I am able to run this workflow in our github enterprise actions but not with ACT. ## Workflow and/or repository - name: checkoutGatewayRepo uses: actions/checkout@v2 with: repository: ${{ steps.get-gateway-repo.outputs.gatewayRepo }} path: konggateway ref: ${{ steps.extract-branch-name.outputs.branch }} token: ${{ secrets.RUNNER_GIT_TOKEN }} ## Steps to reproduce <!-- - Make sure to include full command with parameters you used to run `act`, example: 1. Clone example repo (https://github.com/cplee/github-actions-demo) 2. Enter cloned repo directory 3. Run `act -s SUPER_SECRET=im-a-value` --> ## `act` output <!-- - Use `act` with `-v`/`--verbose` and paste output from your terminal in code block below --> <details> <summary>Log</summary> ```none [ci/build] 🐳 docker exec cmd=[node /var/run/act/actions/actions-checkout@v2/dist/index.js] user= [ci/build] Exec command '[node /var/run/act/actions/actions-checkout@v2/dist/index.js]' [ci/build] ❓ ::save-state name=isPost::true [ci/build] 💬 ::debug::GITHUB_WORKSPACE = '/mnt/c/Users/smelina/dev/code2/apigateway_gitactions-testing' [ci/build] 💬 ::debug::qualified repository = 'https://git.mycompany.com/my-org/my-repo' [ci/build] ❗ ::error::Invalid repository 'https://git.mycompany.com/my-org/my-repo'. Expected format {owner}/{repo}. time="2021-10-17T21:57:15-04:00" level=debug msg="exit with `FAILURE`: 1" [ci/build] ❌ Failure - checkoutGatewayRepo ``` </details>
kerem 2026-03-01 21:44:04 +03:00
Author
Owner

@mssanjay commented on GitHub (Oct 18, 2021):

Sorry. I figured out the issue. Git repo just needs OWNER/REPO and not complete URL. I was then able to use '-s' flag to pass the token. Closing the issue. Thanks

<!-- gh-comment-id:945321478 --> @mssanjay commented on GitHub (Oct 18, 2021): Sorry. I figured out the issue. Git repo just needs OWNER/REPO and not complete URL. I was then able to use '-s' flag to pass the token. Closing the issue. Thanks
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#511
No description provided.