Open ntoskrnl opened 3 years ago
Duplicate of #394
We are also facing the same issue. We are using actions/checkout@v1
It seems related to a Github Actions major outage: https://www.githubstatus.com/
I'm facing the same issue
Same here :(
We are having the same issue as well when trying to checkout additional (tools) repo. Main checkout works as expected.
So any ideas how to fix this?
@yhrabovskyinomi I just created Personal access token and it worked
this is weird. I've re-created same token with same permissions and it started to work too. Magic xD
@ntoskrnl For me, this also started working when creating a new github acces token and adding it to my workflow.
Is someone seeing this again ? There is this which is ongoing at the moment. https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/
Fetching the repository
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
remote: Repository not found.
Error: fatal: repository 'https://github.com/<org>/<repo name>/' not found
The process '/usr/bin/git' failed with exit code 128
Waiting 16 seconds before trying again
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
remote: Repository not found.
Error: fatal: repository 'https://github.com/<org>/<repo name>/' not found not found
The process '/usr/bin/git' failed with exit code 128
Waiting 18 seconds before trying again
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
remote: Repository not found.
Error: fatal: repository 'https://github.com/<org>/<repo name>/' not found' not found
Error: The process '/usr/bin/git' failed with exit code 128
I am also getting the same issue. How to fix it?
We're hitting this as well. In our case we have 2 jobs, both start with a checkout, the first works fine, the second fails on the submodules.
Edit, OK we had to set the setting to not clear the credentials.
We've been using
actions/checkout@v1
with default configuration (no parameters) an everything was ok.Now we are getting error on fetching repo:
It's a private repo in our organization. Here's the full log.
Tried with latest version – same error.