Not able to checkout remote repo using secrets.GITHUB_TOKEN

Not able to check out another private repo using secrets.GITHUB_TOKEN. Below the scenario, check out 1, and 2 works. 3 fails. Is there a limitation for secrets.GITHUB_TOKEN on remote repos?

repo-1 from for which GitHub action is running and repo-2 that it’s trying to checkout is in the same org

jobs:  
  test:
      name: test
      runs-on: self-hosted
      container: node:14-bullseye
      steps:
      - name: Checkout 1
        uses: actions/checkout@v3
        with:
          fetch-depth: 0      
          
      - name: Checkout 2
        uses: actions/checkout@v3
        with:   
            token: ${{ secrets.MY_PAT }}  
            repository: repo-2
            ref: 'main'     
            path: 'path-1'    
            
      - name: Checkout 3
        uses: actions/checkout@v3
        with:
          token: ${{ secrets.GITHUB_TOKEN }} 
          repository: repo-2
          ref: "master"
          path: "path-2"

Error: Fetching the repository /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/master*:refs/remotes/origin/master* +refs/tags/master*:refs/tags/master* remote: Repository not found. Error: fatal: repository ‘https://github.com/xxxxxx/’ not found The process ‘/usr/bin/git’ failed with exit code 128 Waiting 11 seconds before trying again

[igor-imaginemage]

I was facing this same issue and I was able to use a secret only if the secret name is GH_PAT, like this:

token: ${{ secrets.GH_PAT }}

[christianfrstorm]

– All the best Christian Fr stormyhr Wednesday, 05 October 2022, 07:29am +02:00 from Dennis Gentry @.*** :

Yeah, I was never able to get GITHUB_TOKEN to work. My thought was that our tokens need to be blessed by our organization’s SSO or whatever it is, and that can’t ever happen with a GITHUB_TOKEN because it’s a one-time thing that is formed at the start of the action and goes away when it ends. But there’s no GitHub Enterprise documentation about it, so who knows? I’m really not seeing the benefit of this action over a simple shell script. — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you are subscribed to this thread. Message ID: @ github . com>