Github Pull Error Repository Not Found
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us
Fatal Repository Not Found Gitlab
Learn more about Stack Overflow the company Business Learn more about hiring developers push failed failed with error fatal repository not found or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack github does not provide shell access Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Git Push ERROR: Repository not found up vote https://help.github.com/articles/error-repository-not-found/ 73 down vote favorite 13 I am having a very strange problem with git and github. When I try and push, I am getting: git push -u origin master ERROR: Repository not found. fatal: The remote end hung up unexpectedly I added the remote: git remote add origin git@github.com:account-name/repo-name.git Any ideas? git github git-push share|improve this question asked Apr 12 '12 at 1:48 Justin 8,39630104175 2 http://stackoverflow.com/questions/10116373/git-push-error-repository-not-found Stupid question, but I have to ask... did you create the repository on GitHub? –Greg Hewgill Apr 12 '12 at 1:50 1 Yes that is how I got the git remote add origin git@github.com:account-name/repo-name.git. It exists in GitHub, and its a private repo. –Justin Apr 12 '12 at 1:51 1 did you double check your user and repo names? –thescientist Apr 12 '12 at 1:54 2 did u change your github user name –Ankit May 5 '12 at 3:28 1 Same problem, no solution so far. –markus Nov 9 '13 at 21:56 | show 3 more comments 24 Answers 24 active oldest votes up vote 107 down vote I just ran into this issue as well. I had been added to an existing project. I cloned it and committed a local change. I went to push and got the ERROR: Repository not found. error message. I realized that the person who added me only gave me read-only access to the repo. A quick email to him and I'm able to push. Check to see if you have read-write access. Good luck! share|improve this answer answered Apr 19 '12 at 19:04 JT. 1,316178 34 Got
here for a quick overview of the site Help Center Detailed answers to any questions you http://stackoverflow.com/questions/10922028/github-error-repository-not-found-fatal-the-remote-end-hung-up-unexpectedly might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers https://www.skyverge.com/blog/github-repository-not-found-workaround/ or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community repository not of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Github: ERROR: Repository not found. fatal: The remote end hung up unexpectedly (different from similar posts apparently) up vote 23 down vote favorite I created a directory hello_git. In this directory I created a file repository not found hello_git.py which prints out a "Hello git!" message. Then I made hello_git my current directory in the terminal and entered the following commands one after another in that directory: git init git add hello_git.py git commit -m 'first commit' git remote add origin git@github.com:githubaccountname/hello_git.git When I enter the command git push origin master I get asked: Enter passphrase for key '/home/myusername/.ssh/id_rsa': When I enter my passphrase (which authenticates succesfully using ssh -T git@github.com) I get this: ERROR: Repository not found. fatal: The remote end hung up unexpectedly I don't know if this helps, but: git remote -v returns: origin git@github.com:githubaccountname/hello_git.git (fetch) origin git@github.com:githubaccountname/hello_git.git (push) I have looked into answers of similar posts but nothing seems to work: fatal: The remote end hung up unexpectedly while pushing to git repository Github ERROR: Repository not found. fatal: The remote end hung up unexpectedly GitHub - How to resolve this issue of preventing push to origin? git github share|improve this question edi
I was unable to fetch a remote repository to merge into my local clone. Everything seemed to be configured correctly, and I am able to fetch repositories from the same user without a problem, so it seems like there is some issue with this particular repository. Although I have a support ticket open with GitHub to try and determine the root cause of the issue, for now I do have a workaround which I figured I'd share in case it helps anyone out there. The solution essentially is to add the remote repository over the https, rather than git protocol, as described below. The Problem I have a local clone of a repository I forked on GitHub, following the Fork a Repository instructions found on GitHub. This has always worked fine for me, up until today, with this particular repository. Attempting to fetch changes from the remote repository was failing like so: $ git fetch upstream fatal: remote error: Repository not found. Same error for a git remote show as well: $ git remote show upstream fatal: remote error: Repository not found. Adding the verbose flag added no additional information. The Workaround I won't quite call it a ‘solution', but my workaround came from Googling around and learning that a remote repository can be added over a number of protocols. So I removed the remote that I had added with the git protocol per the Fork a Repository instructions, and re-added it over the https protocol: $ git remote rm upstream $ git remote add upstream https://github.com/octocat/Spoon-Knife.git $ git fetch upstream Username: Password: $ git merge upstream/master Note the remote url protocol https://github.com/octocat/Spoon-Knife.git rather than git://github.com/octocat/Spoon-Knife.git. Over the HTTPS protocol everything works as expected, I just have to provide my GitHub username/password, which I did not have to do when the git protocol was working. If I hear back from GitHub support I'll update this article with any further information. Update: Resolu