Error Src Refspec Local Does Not Match Any

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and error src refspec master does not match any policies of this site About Us Learn more about Stack Overflow the error src refspec master does not match any heroku company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users error src refspec master does not match any git 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 error src refspec master does not match any. error failed to push some refs to a minute: Sign up src refspec master does not match any when pushing commits in git up vote 1080 down vote favorite 237 I cloned my repository with: git clone ssh://xxxxx/xx.git but after I changed some files and add and commit them I want to push them to server: git add xxx.php git commit -m "TEST" git push origin master But the

Error Src Refspec Matches More Than One

error I get back is: error: src refspec master does not match any. error: failed to push some refs to 'ssh://xxxxx.com/project.git' git commit share|improve this question edited Apr 23 '14 at 20:32 user456814 asked Nov 15 '10 at 6:09 sinoohe 5,57531112 1 @Marco that question has a lot of noise. This one got to the root of the answer quickly. It's more concise, so it gets my vote. –weberc2 Feb 8 '13 at 3:38 3 @Marco That's not a duplicate. That one is a very specific issue about pushing a local branch to a remote branch. This one is about initializing a repo and pushing it up. They produce the same error, but the REASONS they produce that error and the fixes are entirely different. Also, sinoohe, you should accept an answer. Probably the first one, seeing as it answers the question and has helped over 350 people. –tandrewnichols Jul 8 '13 at 0:42 Did you set up your git config commands to install and configure git globally on your machine? –Igor Ganapolsky Nov 4 '13 at 1:18

be self applied. If you are an Atlassian Cloud customer

Src Refspec Doesn't Match Any

and you wish for Atlassian Cloud Support to perform src refspec master does not match any heroku this procedure for you pleasefile a support request referencingthis article. Problem When pushing error: pathspec 'commit'' did not match any file(s) known to git. a new repository to Bitbucket Server, the following error is returned from the Git client: git push -u origin master error: http://stackoverflow.com/questions/4181861/src-refspec-master-does-not-match-any-when-pushing-commits-in-git src refspec master does not match any. error: failed to push some refs to 'http://stash.company.com/scm/PROJECT/REPO.git' Cause This is caused by the repository still being empty. There are no commits in the repository and thus nomaster branch to push to the server. Resolution https://confluence.atlassian.com/bitbucketserverkb/src-refspec-master-does-not-match-any-error-when-pushing-to-repository-788727186.html Create the first commit inside of the repository and then it can be pushed. For example, the following with create an initial commit and push it to the server. touch initial git add initial git commit -m "initial commit" git push -u origin master Was this helpful? Yes No Thanks for your feedback! Why was this unhelpful? It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © 2016 Atlassian Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.

might be getting and error like... error : src refspec test does not match any. fatal : The remote end hung up unexpectedly http://www.codingdefined.com/2014/07/error-when-git-push-src-refspec-test.html error : failed to push some refs to 'git@github.com: {username}/{projectname}.git' So, In https://github.com/Shippable/support/issues/220 this post we will try to fix this error, we have some solution regarding 'error : src refspec test does not match any'. So, lets list down the solutions.. Solution 1 : At first just try to commit all the files before pushing it into the github. This src refspec error will come when you haven't committed the files and tried to push to the github. If this also doesn't worked out for you, lets move to 2nd solution. Solution 2 : If you are working with branches and getting this error then might be you are not refrencing to the correct branch. Refspec are always in the form not match any source:destination, so the error is telling you that might be something is wrong with your source part. If you are doing a spelling mistake or changing the case of the branch, you will get this error because branch names are case-sensitive. Solution 3 : If above two solution doesn't worked for you then you can try using : git push origin HEAD:master OR git push origin "your_git_repo":"your_branch_name" OR git push origin master --force So these three solution will surely make your "git push" work but if it doesn't just check that you are trying to push a specific branch in local to a specific branch in remote. This error will also come when you are in a specific branch and try to push another that do not exist yet. Please Like and Share the Blog, if you find it interesting and helpful. Related articles readFile Vs createReadStream in Nodejs 10 Interview Questions on Nodejs Utilities Module in Nodejs Use of Redis in Nodejs 5 Tips for Beginner Nodejs Developers Use of cluster in Nodejs Crossroads : Router

Sign in Pricing Blog Support Search GitHub This repository Watch 52 Star 80 Fork 14 Shippable/support Code Issues 123 Pull requests 0 Projects 0 Pulse Graphs New issue Heroku push error: src refspec develop does not match any #220 Closed aliismayilov opened this Issue Jun 17, 2014 · 6 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 5 participants aliismayilov commented Jun 17, 2014 I followed instructions on documentation (e.g. added deployment key from this url to this url). Here is my shippable.yml: language: ruby rvm: - 2.1.2 before_script: - psql -c 'create database edu_rails_test;' -U postgres - mkdir -p shippable/testresults env: - CI_REPORTS=shippable/testresults COVERAGE_REPORTS=shippable/codecoverage script: - rspec --format RspecJunitFormatter --out shippable/testresults/results.xml after_success: - git push git@heroku.com:edu-rails-staging.git develop:master Build is passing fine. But I get the following error on after_success: git push git@heroku.com:edu-rails-staging.git develop:master Warning: Permanently added the RSA host key for IP address 50.19.85.156 to the list of known hosts. Fetching repository, done. error: src refspec develop does not match any. error: failed to push some refs to git@heroku.com:edu-rails-staging.git It works fine if I try to push from local machine. aliismayilov commented Jun 17, 2014 I am trying to push from develop branch to the staging app on Heroku. rageshkrishna commented Jun 17, 2014 @aliismayilov When we clone your repository from GitHub, master is the only local branch that gets created. We do a git reset --hard to get HEAD to point to the commit that needs to be built. You can see this happening in the console log output on your build. Because we do it this way, we don't really need to declare a new local branch before building. This is why you get an error saying no refspec matches "develop". You can use git push HEAD:master instead to push the current code to Heroku. aliismayilov commented Jun 17, 2014 @rageshkrishna thank you! Worked. aliismayilov closed this Jun 17, 2014 seoyoochan commented Sep 23, 2014 thank you!! dimoni414 commented Apr 5, 2016 @rageshkrishna Thank you! snamoah commented Sep 1, 2016 Thanks @rageshkrishna. It worked for me too Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment