repository not found

[DgRosa]

[edited by @ericsciple] Sorry for the disruption. There is an active incident right now that is causing the GITHUB_TOKEN to not have permission to checkout private repos.

Everything was working fine until all of the sudden this error started to popup and I have no idea why.
Can it be a GitHub service issue or maybe a recent release that introduced a bug.
It's a private repository I don't know if that can help debug the issue.

Workflow stack

/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +7f692a64151c6ae3be4518df16d88b891eb76c1b:refs/remotes/origin/master
  remote: Repository not found.
  ##[error]fatal: repository 'https://github.com/DgRosa/likacrm/' not found
  The process '/usr/bin/git' failed with exit code 128

[ryanmiriyagalla]

+1 on this. Github actions suddenly started giving this error.
"Investigating - We are investigating an increase in errors on GitHub.com."
I think this is due an error in github. Check https://www.githubstatus.com/

[bigfootjon]

I think it's something to do with private repos? I just reran some public repo actions and they worked correctly, but my private repos are failing every time.

[dcarlstedt]

I am also having this exact same issue. It started appearing somewhere in the last hour to our private repos.

[sergeh]

+1 also just started to happen on our private repos

[mcbanderson]

Happening on my private repos as well, for both v1 and v2.

Edit: Looks like GitHub is experiencing some service degradation, so this could be a GitHub issue and not an issue with this action.

[faizanakram99]

Same, was about to open an issue.

Didn't know whether it is related to this repository or to GitHub

[brettpalmberg]

+1 . Same issue with GitHub Actions and private repos.

[Albinzr]

Same issue all the build process is stuck for me

[dianhsu]

Oops....

[patrickk]

+1, same here. Repo exists.

[Albinzr]

Are the any alternatives for checkout that can be used as fallback

[Andrew-Kulpa]

I'm experiencing this issue too! 👍

[belalessandro]

Same for me

[pinkstrings]

Anyone know if this is an issue with Github itself, or specific to the code in this action?

[ilgooz]

Anyone know if this is an issue with Github itself, or specific to the code in this action?

Probably due to an issue with Github APIs. We are using a fixed version of checkout which is @v2 and still experiencing this issue.

@ericsciple can you please report this issue to the team?

---

I got more news, the status page is yellow, there seems to be an incident ATM. See: https://www.githubstatus.com/

[cfbao]

Anyone know if this is an issue with Github itself, or specific to the code in this action?

Pretty sure it has nothing to do with the checkout action.
The latest code change is yesterday, but it was running fine this morning.

[veich]

@github Team - that's why you don't do deployments on Friday 😁

EDIT: November 27th 2020 - repeat error & they did it again on Friday 🤦 😂

[handhead-dev]

+1

[ericsciple]

@ilgooz there is an ongoing investigation - it's known. Not an issue w/ this repo as you mentioned.

[ivandimitrovSC]

Thanks for this issue! I literally merged our first workflow 90 minutes ago and have been debugging the broken CI ever since. Knowing it's service degradation is of some relief.

[AnthonyKinson]

+1 same thing just started happening in our org private repos

[PrinsFrank]

Only affects our private repos, public ones still work fine.

[weihao]

Adding logs

  remote: Repository not found.
  ##[error]fatal: repository 'https://github.com/user/repository/' not found
  The process '/usr/bin/git' failed with exit code 128

[finnkauski]

Same here. Issue with private repo deployment. Spent like and hour figuring it out. Feel like such an idiot not having a look here first!

[batok]

When actions/checkout runs fetches the master version of this repo? I mean github tries to fetch the most recent version?

[Hirrolot]

Does anybody know an up-to-date workaround? Got this issue today. None of the above workarounds worked for me.

UPD: setting up a custom organization-level personal access token and using it instead of GITHUB_TOKEN worked. This issue seems to be a problem with GITHUB_TOKEN specifically.

[stauffenberg2020]

UPD: setting up a custom organization-level personal access token and using it instead of GITHUB_TOKEN worked. This issue seems to be a problem with GITHUB_TOKEN specifically.

Did not work with organization-level PAT. Can you give a step by step info on what you did in detail and how you created the organization-level PAT?

[Hirrolot]

@stauffenberg2020, go to https://github.com/settings/tokens and create a new token. Set no expiration date, and click on the "repo" scope in access permissions. Then go to https://github.com/organizations/<your-organization>/settings/secrets/actions and set ORG_TOKEN to the newly created token. Then use ORG_TOKEN instead of GITHUB_TOKEN in problematic places.

[stauffenberg2020]

@Hirrolot

Then go to https://github.com/organizations/<your-organization>/settings/secrets/actions and set ORG_TOKEN to the newly created token.

The above option exist only for for public repositories in the org.

The whole point of this issue is that the org repository also being private. Are you talking about paid accounts?

[Hirrolot]

@stauffenberg2020, my repositories are private. I use the team plan. However, just using GITHUB_TOKEN didn't work even for me.

[stauffenberg2020]

Thanks @Hirrolot

I use the team plan.

I "guess" this is making the difference. If possible, can you set up an org/account/repo in free plan and see if it works or not?

[Hirrolot]

I "guess" this is making the difference. If possible, can you set up an org/account/repo in free plan and see if it works or not?

Well, there's no option to set up organization-level secrets for private repositories in the free plan (your screenshot shows it). So my workaround is only for paid subscriptions.

[MiltiadisKoutsokeras]

Thank you all for the workarounds, we may apply them on our organization. But this still does not explain the fact that the same setup is working in some projects and fails in a few new ones. We use SSH deployment keys for repositories that need to be accessed inside GitHub actions and use webfactory/ssh-agent to add private keys during runtime. It works like a charm in most project and fails in others. The issue is that the Action cannot access the repo it runs for, not the repos accessed via deployment keys.

Which of these reasons could this be?

UPDATE: I have just created a new test project in my own repositories instead of organization team. I used the same project template and used the same setup as the failing projects. It passes all Actions successfully. I am starting to think if there is something in the GitHub back-end we do not control that causes the problem in some projects.

[JeanBlignaut]

I'm experiencing the same issue on a new org and private repo I created yesterday.

[JeanBlignaut]

Interestingly I see that one of the action runs succeeded but since I'm new to actions and new to azure functions (what I'm trying to deploy) I'm still figuring out how to debug...

[douile17]

Same problem here ...

[steinelg]

I all of a sudden ran into this issue today, when attempting to apply this action to an company internal github repo.

Changing

permissions:
actions: read
pages: write
id-token: write

to

permissions:
actions: read
contents: read
pages: write
id-token: write

seems to have fixed it for me at least.

(using actions/checkout@v3)

[maurigvs]

Just ran into this issue today with a company github repo. Still have not find a solution.

[lilac]

Me too. It used to work well, but started throwing this error from yesterday.

The workaround is add the contents permission, if it's not there.

permissions:
  contents: read

[danieldelarosaagility]

permissions:
  contents: read

Updating the permissions as described above does not work for a private repo.

I'm having this issue with both actions/checkout@v3 and actions/checkout@v4

[maurigvs]

I solved my problem, passing the secrets from the called workflow to the called workflow.

My context is enterprise internal repositories.

[mialdi98]

Resolved my issue

permissions:
  contents: read
  packages: write

and here where to use it:

name: GitHub Actions
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
permissions:
  actions: write       # Necessary to cancel workflow executions
  checks: write        # Necessary to write reports
  pull-requests: write # Necessary to comment on PRs
  contents: read
  packages: write
on: [pull_request]
jobs:
  setup_dependencies:
    timeout-minutes: 120
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout repo
        uses: actions/checkout@v4
        with:
          token: ${{ secrets.GITHUB_TOKEN }}

[jmcconathy]

These workaround are not working for me either.

Both repositories are in the same organization. And the second repo is configured to be available to workflows in the org (I have also tried setting it to be available to workflows enterprise wide but to no difference in outcome).
My workflow still says the repo was not found.
If i make the repo public it works, and if i set an organizational token (which i cant make last longer than 90 days), then it works fine.

[lvl99]

I'm working in a private repo which is part of an org with SSO enabled. I'm using an action which sets PR comments so had permissions configured:

permissions:
  pull-requests: write

I got the "repository not found" error, to which this thread helped me by suggesting I add the contents: read line:

permissions:
  contents: read
  pull-requests: write

Seemed to work! Thanks all.

[markanthonyuy]

I wish github can provide a better error message regarding this issue. It's really the permissions that's causing this

[ampcpmgp]

This occurred in the public repository. I tried the workaround and still got the error.

I wrote the following clone command to work around it.

git clone --depth 1 --branch ${{ github.ref_name }} --single-branch https://github.com/ampcpmgp/elemental-sea.git .

[dralshehri]

I found that for jobs with any permissions set, I need to set other permissions, too; otherwise, they will default to none.

To fix the checkout issue, I added contents: read to permissions, which works for me.

For reference:

If you specify the access for any of these scopes, all of those that are not specified are set to none.

👆🏼 from Defining access for the GITHUB_TOKEN scopes

[vgundavarapu]

I am still getting this issue and mine is a private repo from which I am trying to pull and I tried the permissions fix which was suggested by others and still seeing the issue

[pritisolanki]

It is still a issue