Knowledge map advanced must read: read how large-scale map data efficient storage and retrieval>>>
1. fatal: ‘origin’ does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Fatal: “origin” is not a git repository
Fatal: unable to read the remote repository
Make sure you have the correct access rights and that the repository exists
Solution: 1. First, check that your origin is set to run
git remote -v
Display
orgin [email protected] :chaorwin/chaorwin.git (fetch)
orgin [email protected] :chaorwin/chaorwin.git (push)
“Origin” does not exist
2. Rename it, or change the URL, delete it, and then add the correct one
git remote remove orgin
3. Add one
git remot add origin [email protected] :chaorwin/chaorwin.git
4. git push origin master
Similar Posts:
- [Solved] Git push origin master fatal: ‘origin’ does not appear to be a git repository fatal…
- Git Unable to switch remote branches error: pathspec ‘origin/XXXX’ did not match any file(s) known to git
- How to Solve Code cloud error: fatal: remote origin already exists
- How to Solve error: failed to push some refs to ‘xxxx’
- [Solved] error: failed to push some refs to ‘xxxx’
- fatal:’origin’ does not appear to be a git repository fatal:Could not read from remote re…
- [Solved] Git pull fatal: refusing to merge unrelated histories
- GitHub common operations and common errors! Error prompt: fatal: remote origin already exists
- Git submits the code to the remote warehouse with an error: fatal: remote origin already exists
- Git push Warning: The authenticity of host ‘github.com (52.74.223.119)’ can’t be established.