GET Remote Repo 404 (Not Found)
See original GitHub issueDescription
Loggers when additional remote no longer exists.
Version
- GitHub Desktop: 1.3.5-beta0
- Operating system: Windows 10
Steps to Reproduce
- Clone a repo (Desktop for example)
- Fork it to your personal account
- Add it as a remote, and checkout a branch from the remote on your personal account
- Delete the remote repo
- See the loggers 🔥.
Expected Behavior
Warn user that remote no longer exists.
Actual Behavior
Nothing really.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
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 >Git command returns "not found" or error code 404
Cause. The project and/or repository do not exist, or you do not have permissions to view this repository.
Read more >404 when cloning newly created Git Repository - MSDN
Error encountered while cloning the remote repository: Response status code does not indicate success: 404 (Not Found).
Read more >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 >[bug] ERROR: 404: Not Found. [Remote: conan-center] #8293
Some of my coworkers came up with the following problem: When they run conan install .. -b missing from the build folder, they...
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
How about switching the push/pull button back to the “publish repository” button if the remote can’t be accessed?
I am of the belief it is best to:
Vs