Hello,

Thank you for your time working on this GHA.
The following line seems to have a problem when used with a Github Application Token.

When using a token from a Github Application, the if/then will result in false, setting is-repo-exists-and-has-ref to false.

If you use oauth2: or : as the value of inputs.token the check will work as expected in my case, resulting in a true result, setting is-repo-exists-and-has-ref to true.

Unfortunately, checkout/v3 DOES work with a Github Application Token - https://github.com/andry81-devops/gh-action--git-checkout/blob/master/action.yml#L67

So the workaround for the git ls-remote causes a failure with checkout/v3 :(

I do not know if you can use the oauth2: syntax when using a PAT token.

The second possible problem is that the command is not actually checking the ref input.

The command to do so should be git ls-remote -q --exit-code "https://${{ inputs.token }}@github.com/${{ inputs.repository }}" ${{ inputs.ref }} > /dev/null 2>&1

Thank you for your time.

This is the error:

And the error: Process completed with exit code 2.

To add more context, this is what I do before you action is executed:

      - name: Create Repository
        uses: repo-ctrl/create-repo-action@main 
        id: create-repo
        with:
          org-admin-token: '${{secrets.MY_PAT}}'
          repo-name: '${{github.event.inputs.repository_name}}'
      
      - name: Initialize Default Branch
        uses: peterjgrainger/[email protected]
        env:
          GITHUB_TOKEN: '${{secrets.MY_PAT}}'
        with:
          branch: '${{env.DEFAULT_BRANCH}}'

      - uses: andry81-devops/gh-action--git-checkout@master
        with:
          token: '${{secrets.MY_PAT}}'
          repository: '${{github.event.repository.owner.login}}/${{github.event.inputs.repository_name}}'
          ref: '${{env.DEFAULT_BRANCH}}'
          path: '${{env.NEW_REPO_WORK_DIR}}'
          mkdir-p: >-

The repo is created, so the PAT works.
It was working before, since I used it extensively around 6 months ago.
This is not issue of disabled action scripts after period of inactivity, since I have automated action running once a week.

Any ideas?