-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repository not found #254
Comments
+1 on this. Github actions suddenly started giving this error. |
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. |
I am also having this exact same issue. It started appearing somewhere in the last hour to our private repos. |
+1 also just started to happen on our private repos |
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. |
Same, was about to open an issue. Didn't know whether it is related to this repository or to GitHub |
+1 . Same issue with GitHub Actions and private repos. |
Same issue all the build process is stuck for me |
Oops.... |
+1, same here. Repo exists. |
Are the any alternatives for checkout that can be used as fallback |
I'm experiencing this issue too! 👍 |
Same for me |
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 @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/ |
Pretty sure it has nothing to do with the checkout action. |
@github Team - that's why you don't do deployments on Friday 😁 EDIT: November 27th 2020 - repeat error & they did it again on Friday 🤦 😂 |
+1 |
@ilgooz there is an ongoing investigation - it's known. Not an issue w/ this repo as you mentioned. |
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. |
+1 same thing just started happening in our org private repos |
Only affects our private repos, public ones still work fine. |
Adding logs
|
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! |
When actions/checkout runs fetches the master version of this repo? I mean github tries to fetch the most recent version? |
Thanks @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. |
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 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. |
I'm experiencing the same issue on a new org and private repo I created yesterday. |
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... |
Same problem here ... |
I all of a sudden ran into this issue today, when attempting to apply this action to an company internal github repo. Changing permissions: to permissions: seems to have fixed it for me at least. (using actions/checkout@v3) |
Just ran into this issue today with a company github repo. Still have not find a solution. |
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.
|
Updating the permissions as described above does not work for a private repo. I'm having this issue with both |
I solved my problem, passing the secrets from the called workflow to the called workflow. My context is enterprise internal repositories. |
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 }} |
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). |
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:
pull-requests: write I got the "repository not found" error, to which this thread helped me by suggesting I add the permissions:
contents: read
pull-requests: write Seemed to work! Thanks all. |
I wish github can provide a better error message regarding this issue. It's really the |
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 . |
I found that for jobs with any permissions set, I need to set other permissions, too; otherwise, they will default to To fix the checkout issue, I added For reference:
|
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 |
It is still a issue |
Ran into this issue today. Generate a personal access token with read permission for both the repository you are trying to install as a package as well as the repository the action is for. In your deploy.yml explicitly set the token like so. Also in the repository you are trying to install, go to settings -> actions -> general -> access -> click the radio option that says "Accessible from repositories in the 'abc' organization" and save |
I ran into the same issue using GitHub App authentication for my organization |
After so many months of having this issue is some repositories I start to believe that the problem has a possibility of being caused by back-end configuration that is not controlled by the end-user. No matter what I applied from the suggestions in this thread does not fix the issue and newly created repositories with the exactly the same CI/CD setup do not reproduce the issue. |
Seems to still be an issue |
Same. |
I ended up making a dedicated GitHub user with specific permissions for doing work in the context of Actions, and it resolved this issue for me. I read somewhere that this was the recommended pattern but now I don't see it in the readme. |
[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
The text was updated successfully, but these errors were encountered: