Error: fatal: repository not found (private repo)
See original GitHub issueAnyone else getting this? This just started yesterday evening and still getting it. The repository does exist and this flow used to work fine earlier in the day.
...
- name: "Checkout"
uses: actions/checkout@v2
with:
fetch-depth: 0
- run: |
git checkout ${{ github.event.inputs.ref }}
...
Error: fatal: repository 'https://github.com/bitsofinfo/my-private-repo/' not found
The process '/usr/bin/git' failed with exit code 128
Waiting 12 seconds before trying again
/usr/bin/git -c protocol.version=2 fetch --prune --progress --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/*
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:7
Top Results From Across the Web
Fix Git's 'fatal: repository not found' error quickly | TheServerSide
Fix Git's repository not found error · 1. You did not authenticate · 2. Your password has changed · 3. You are not...
Read more >github - Git - remote: Repository not found - Stack Overflow
Open Control Panel from the Start menu. · Select User Accounts. · Select the "Credential Manager". · Click on "Manage Windows Credentials". ·...
Read more >[Fix] 'Fatal: Repository Not Found' Error In Git - Tech News Today
When cloning a repository or pushing changes to it, you may encounter the Repository Not Found error. At first glance, the error message...
Read more >[Fixed] Git - remote: Repository not found in 9 ways (Windows ...
5. Fix 4 - Git - remote: Repository not found · Go to the git folder and go inside the .git folder ·...
Read more >Solving “Fatal: Not A Git Repository” (Or Any Of The Parent ...
The error stated above indicates that you possess an authenticated useraddname-password pair, but you do not maintain the files in the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
had same issue… what I did to fix it
I noticed once the origin is removed and added again, it fixes the error hopefully this helps
the only way I could get it to work again is to go into your settings on your repo and REVOKE all access to it for github actions, save… then re-grant access for github actions. For whatever reason, next time I ran it, it has its access back.