Git Submodule Error Repository Not Found
Contents |
found mac windows linux all If you see this error when cloning a repository, it means that the repository does not exist or you do not have remote: repository not found. fatal: repository not found permission to access it. There are a few solutions to this
Git Push Fatal Remote Error Repository Not Found
error, depending on the cause. Check your spelling Typos happen, and repository names are case-sensitive. If you try fatal repository not found bitbucket to clone git@github.com:user/repo.git, but the repository is really named User/Repo you will receive this error. To avoid this error, when cloning, always copy and paste the clone URL from github clone private repo the repository's page. For more information, see "Cloning a repository." To update the remote on an existing repository, see "Changing a remote's URL". Checking your permissions If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error. Make sure that you have access to the repository in
Github Check Permissions
one of these ways: The owner of the repository A collaborator on the repository A member of a team that has access to the repository (if the repository belongs to an organization) Check your SSH access In rare circumstances, you may not have the proper SSH access to a repository. You should ensure that the SSH key you are using is attached to your GitHub user account. You can check this by typing the following into the command line: ssh -T git@github.com Hi username! You've successfully authenticated, but GitHub does not provide shell access. For more information, see Adding a new SSH key to your GitHub account. Check that the repository really exists If all else fails, make sure that the repository really exists on GitHub! If you're trying to push to a repository that doesn't exist, you'll get this error. Contact a human Article versions GitHub.com GitHub Enterprise 2.7 GitHub Enterprise 2.6 GitHub Enterprise 2.5 GitHub Enterprise 2.4 GitHub Enterprise 2.3 © 2016 GitHub Inc. All rights reserved. Terms of Service Privacy Security Support
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 github does not provide shell access About Us Learn more about Stack Overflow the company Business Learn more about fatal repository not found gitlab hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss
Push Failed Failed With Error Fatal Repository Not Found
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 minute: Sign up Git Push ERROR: https://help.github.com/articles/error-repository-not-found/ Repository not found up vote 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 http://stackoverflow.com/questions/10116373/git-push-error-repository-not-found '12 at 1:48 Justin 8,39630104175 2 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|im
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 http://stackoverflow.com/questions/22049777/private-git-submodule-not-found-in-jenkins Overflow the company Business Learn more about hiring developers or posting ads with us https://salferrarello.com/git-submodule-fatal-read-remote-repository/ Stack Overflow Questions Jobs Documentation Tags Users 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 minute: Sign up Private git submodule not found in Jenkins up vote 4 down vote favorite 2 The repository not problem I'm trying to build my application in Jenkins, and it is on a private repo on Github, also there's a private submodule. I can clone the private repository in Jenkins by setting up it's credentials, but Jenkins can't clone the submodule, here's the output of a failed build: Started by an SCM change Building in workspace /var/lib/jenkins/jobs/Project/workspace Fetching changes from the remote Git repository Fetching upstream changes from git@github.com:user/repogit using repository not found GIT_SSH to set credentials Checking out Revision 9cc99b67cc676d0ea8ccd489a8327f5c6dbb8d7f (origin/branch) [workspace] $ /bin/sh -xe /tmp/hudson2710403018107019432.sh + git submodule update --init --recursive Initialized empty Git repository in /var/lib/jenkins/jobs/repository/submodule/.git/ ERROR: Repository not found. fatal: The remote end hung up unexpectedly Clone of 'git@github.com:user/submodule.git' into submodule path 'repository/submodule/' failed Build step 'Execute shell' marked build as failure Discard old builds... #156 is removed because status FAILURE is not to be kept Publishing Clover coverage report... No Clover report will be published due to a Build Failure Sending e-mails to: Finished: FAILURE Here's what I've tried to do in Jenkins Tried to set the Additional behavior "Advanced sub-module behavior", with no success. Tried to set up a new step before running the tests with phpunit: git submodule update --init --recursive Tried to set a git repository on the project of my submodule too, not just the main repository that is being tested, no luck too. All of them causes the error that says that Jenkins can't find the repository of the submodule. Any ideas of how can I solve this? (The username, paths and repositories are correct, I've just changed them to post here) php git jenkins git-submodules jenkins-php share|improve this question asked Feb 26 '14 at 18:14 Brayan 231111 add a comment| 1 A
I Build WordPress Themes with Bootstrap Yoast SEO Eliminate Notifications You are here: Home / Computing / Git Submodule fatal: Could not read from remote repositoryGit Submodule fatal: Could not read from remote repository Last updated on April 18, 2014 by Sal Ferrarello 2 Comments Why to Setup Your Git Submodules as https:// not ssh I was pulling a public GitHub repo the other day which featured submodules. The frustrating problem is whenever I tried to init the submodules with the line git submodule update --init --recursive I got the error Git Submodule fatal: Could not read from remote repository The Issue This comment on Stack Overflow was the key to understanding the issue using a GitHub public url rather than using a public key. I was cloning a public GitHub repo and the submodules were also public GitHub repos but I don't use SSH authentication for GitHub, I use credential.helper osxkeychain and the submodule urls were using the format git@github.com:mileszs/ack.vim.git rather than https://github.com/mileszs/ack.vim.git. The former format requires you access GitHub via SSH, the later allows any public connection. Please Setup Submodules Using Public URLs The take-away from all of this is, please use public URLs (https://) not SSH (git@github.com:) when setting up your submodules. Please Use this git submodule add https://github.com/salcode/example.git Not This git submodule add git@github.com:salcode/example.git Filed Under: Computing Tagged With: GitComments this guy says May 12, 2014 at 11:17 pm I have fun with, result in I found exactly what I was having a look for. You have ended my 4 day lengthy hunt! God Bless you man. Have a great day. Bye Reply Sal Ferrarello says May 13, 2014 at 6:10 am Glad to hear this article helped. Thanks. Reply Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website WordCamp Baltimore 2016 WordCamp US 2016 Sal Ferrarello Web Developer specializing in WordPress, contributor to Genesis Framework, author of the Bootstrap Genesis Theme, author of the WordPress Stop Emails plugin, available for development work as Iron Code Studio Search Tags ajax AWS Bootstrap