Repository not found

[chingc]

Sorry, I don't know if this is the right place to post this, but today I've been having issues with actions/checkout@v2 where it would fail to checkout my repository. The error says my repository is not found. However, it wasn't happening all the time.

I had some workflows that didn't fail and those were all using my personal access token. After I updated my failing workflows to use a PAT my builds starting running again.

- uses: actions/checkout@v2
  with:
    token: ${{ secrets.MY_TOKEN }}

Could the default authentication token obtained by actions/checkout be bad?

[dasasathyan]

I started seeing this today in the morning.. 😕

[tsargent]

Same here. I was not able to push new commits to the remote, due to the repository not found error. I created my own personal access token, added it as a secret, and used that as the token value and it worked.

[tsira]

also seeing this behavior

fatal: not in a git directory when running a git cmd

[phamnhuvu-dev]

I am facing too.

[steve-taylor]

Can someone please explain what causes this and how to work around it?

Some say that switching to a PAT fixes it (e.g. with: token: ${{ secrets.MY_TOKEN }}), but my experience is the opposite: It broke when I started using a PAT.

Some say it's caused by GitHub outages, but there's no outage at the moment.

Some say fetch-depth: 0 should be used, but I'm already using it and it's still broken.

Some say that the git version has to be at least 2.18, but I'm running on ubuntu-latest which uses git 2.33.0.

All these reasons have so far been incorrect.

[qitpydev]

for who, you are calling reusable workflow in an Internal repositories.
-> Make sure the workflow permissions should only set in "caller" instead of the "called"