Git Fetch Upstream Remote 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 Learn more about Stack Overflow the company Business Learn remote repository not found. fatal repository more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags git push fatal remote error repository not found Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, fatal repository not found gitlab 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
Fatal Repository Not Found Bitbucket
a directory hello_git. In this directory I created a file 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 github check permissions (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 edited Sep 11 '12 at 20:49 asked Jun 6 '12 at 20:47 Bentley4 3,23694494 3 I think hello_gitty would be a much better name for a sandbox/testing repo! :p –ThiefMaster♦ Jun 6 '12 at 20:49 1 Does the repository actually exist on github? –Eric Jun 6 '12 at 20:50 There is no repository of it on github, I thought it autocreated that for me. Solved. Could you post a seperate post for this so I can vote it as the correct answer? –Bentley4 Jun 6 '12 at 20:52 @Bentley4: There's your problem. I'd say the error message is very clear. –Eric Jun 6 '12 at 20:54 add a comment| 6 Answers 6 active oldest votes up vote 23 down vote accepted The error message says it all ERROR
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and push failed failed with error fatal repository not found policies of this site About Us Learn more about Stack Overflow the company
Github Does Not Provide Shell Access
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Github Check Access Rights
Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a http://stackoverflow.com/questions/10922028/github-error-repository-not-found-fatal-the-remote-end-hung-up-unexpectedly minute: Sign up What does the Git error “remote: Repository not found.” mean? up vote 5 down vote favorite 4 After I issued git push origin
e's how I fixed it, I was able to solve repository not found by opening .git/config and removing the [remote "origin"] section. [remote "origin"] url = git@github.com:jrobertson/dynarex.git fetch = +refs/heads/*:refs/remotes/origin/* then I ran the following (again) git remote add origin git@github.com:jrobertson/dynarex.git git push -u origin master Resources github - Git Push ERROR: Repository not found [stackoverflow.com] Tags:githubrepositoryerrorsolved Source:2214hrs.txt Published:17-03-2013 22:14
攻撃的または迷惑な内容を含んでいます 不適切な内容を含んでいます 送信6ストック0コメントストックストック済み解除 この記事は最終更新日から1年以上が経過しています。privateリポジトリをforkして作業している最中に、fork元の変更を取り込もうとして git remote add upstream git://github.com/foo/bar.git git fetch upstream としたら >fatal: remote error: > Repository not found. となった。forkしなおすといけるけど格好わるい。 解決策 privateリポジトリの場合はgit:ではなくhttps:を使え、ということらしい。 なので、正しくはこうしよう。 git remote add upstream https://github.com/foo/bar.git git fetch upstream >Username for 'https://github.com': >assword for 'https://username@github.com': (おまけ)前の設定を消す git remote add upstream https://github.com/foo/bar.git で > fatal: remote upstream already exists. となったら git remote rm upstream で、前の設定を消そう。 (おまけ)状況確認 自分のローカルとfork元との間の設定はどうなってんだっけ、の時: git remote -v >origin git@github.com:username/bar.git (fetch) >origin git@github.com:username/bar.git (push) >upstream https://github.com/foo/bar.git (fetch) >upstream https://github.com/for/bar.git (push) 参考 http://www.skyverge.com/blog/github-repository-not-found-workaround/ privateリポジトリをforkして作業している最中に、fork元の変更を取り込もうとして ``` git remote add upstream git://github.com/foo/bar.git git fetch upstream ``` としたら ``` >fatal: remote error: > Repository not found. ``` となった。forkしなおすといけるけど格好わるい。 #解決策 privateリポジトリの場合はgit:ではなくhttps:を使え、ということらしい。 なので、正しくはこうしよう。 ``` git remote add upstream https://github.com/foo/bar.git git fetch upstream >Username for 'https://github.com': >assword for 'https://username@github.com': ``` ##(おまけ)前の設定を消す ``` git remote add upstream https://github.com/foo/bar.git ``` で ``` > fatal: remote upstream already exists. ``` となったら ``` git remote rm upstream ``` で、前の設定を消そう。 ##(おまけ)状況確認 自分のローカルとfork元との間の