Git push u origin master выдает ошибку

I just started using git with github. I followed their instructions and ran into errors on the last step. I’m checking in an existing directory that isn’t currently source-controlled (project about a week old). Other than that, my use case should be pretty run of the mill.

Here’s what’s happening:

$ git push origin master
error: src refspec master does not match any.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to 'git@github.com:{username}/{projectname}.git'

Github’s instructions:

Global setup:

  Download and install Git
  git config --global user.name "Your Name"
  git config --global user.email {username}@gmail.com

Next steps:

  mkdir projectname
  cd projectname
  git init
  touch README
  git add README
  git commit -m 'first commit'
  git remote add origin git@github.com:{username}/{projectname}.git
  git push origin master

The error message leads to the conclusion that you do not have a master branch in your local repository. Either push your main development branch (git push origin my-local-master:master which will rename it to master on github) or make a commit first. You can not push a completely empty repository.

I had the same issue. I deleted the .git folder then followed the following commands

1. $ git init
2. $ git add .
3. $ git remote add origin git@gitorious.org:project/project.git
4. $ git commit -m "Initial version"
5. $ git push origin master

I just had the same problem while creating my first Git repository ever. I had a typo in the Git origin remote creation — turns out I didn’t capitalize the name of my repository.

 git remote add origin git@github.com:Odd-engine

First I removed the old remote using

git remote rm origin

Then I recreated the origin, making sure the name of my origin was typed EXACTLY the same way my origin was spelled.

git remote add origin git@github.com:Odd-Engine

No more error! 🙂

answered Apr 9, 2012 at 22:21

I had the same error, as Bombe said I had no local branch named master in my config, although git branch did list a branch named master…

To fix it just add this to your .git/config

[branch "master"]
    remote = origin
    merge = refs/heads/master

Kinda hacky but does the job

answered Aug 13, 2009 at 12:59

make sure you are on a branch, at least in master branch

type:

git branch

you should see:

ubuntu-user:~/git/turmeric-releng$ git branch

* (no branch)
master

then type:

git checkout master

then all your changes will fit in master branch (or the branch u choose)

answered Sep 9, 2011 at 18:22

error: failed to push some refs to 'git@github.com:{username}/{projectname}.git'

Unless you’re generalizing the error message, it looks like you literally put git@github.com:{username}/{projectname}.git as your remote Git repo. You should fill in {username} with your GitHub username, and {projectname} with your project’s name.

answered Sep 15, 2009 at 22:01

It looks like this question has a number of answers already, but I’ll weigh in with mine since I haven’t seen any that address the issue I had.

I had this error as well on a brand new github repository. It turns out the user I was pushing from did not have push access. For some reason, this results in an «ERROR: repository not found» error instead of some sort of access error.

Anyway, I hope this helps the poor soul who runs into the same issue.

answered Apr 23, 2012 at 22:20

i fixed my problem….

not sure what the problem was but using the gitx interface to commit my staged files, then…

$ git push origin master

worked…

i am having the same problem…

created a new folder added in the bort template files…

$ git commit -m 'first commit'

$ git remote add origin git@github.com:eltonstewart/band-of-strangers.git

$ git push origin master

then i get the same error…

error: src refspec master does not match any.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to ‘git@github.com:eltonstewart/band-of-strangers.git’

cd  app 

git init 

git status 

touch  test 

git add . 

git commit  -a  -m"message to log " 

git commit  -a  -m "message to log" 

git remote add origin 

 git remote add origin git@git.google.net:cherry 

git push origin master:refs/heads/master

git clone git@git.google.net:cherry test1

answered Feb 4, 2012 at 17:59

answered Dec 18, 2020 at 1:05

answered Mar 6, 2010 at 23:20

answered Mar 7, 2010 at 10:33

answered Mar 13, 2010 at 21:20

Initital add & commit worked like a charm. I guess it’s just a matter of understanding Git’s methodology of managing a project within the repository.

After that I’ve managed to push my data straight-away with no hassle.

answered Mar 28, 2011 at 16:28

I just encountered this problem, and it seemed to be caused by my not adding a custom commit message above the default commit message (I figured, why write «initial commit», when it clearly says that very same thing in the Git-generated text below it).

The problem resolved when I removed the .git directory, re-initialized the project directory for Git, re-added the GitHub remote, added all files to the new stage, committed with a personal message above the auto-generated message, and pushed to origin/master.

answered Jun 13, 2014 at 23:46

When you create a repository on Github, It adds a README.md file to the repo and since this file might not be there in your local directory, or perhaps it might have different content git push would fail.
To solve the problem I did:

git pull origin master
git push origin master

This time it worked since I had the README.md file.

answered Sep 6, 2014 at 22:30

answered Oct 10, 2014 at 16:35

This is very old question but for all new people who will end up here like me.
This solution is only for

error: src refspec master does not match any.

error for new repo created

You need to add your

git config user.email "your email"
git config user.name "name"

Only after adding email and name add files to git and commit

git add .
git commit -m "message"

It will work like charm

answered Feb 16, 2015 at 13:03

I have this error too, i put a commit for not push empty project like a lot of people do but doesn’t work

The problem was the ssl, y put the next

git config —system http.sslverify false

And after that everything works fine 🙂

git push origin master

answered Feb 16, 2016 at 4:48

answered Sep 12, 2016 at 10:54

answered Sep 15, 2019 at 17:38

Bumping an old thread.

If you have created a repository on Github with a Readme or a .gitignore, you might have to rebase the local master with the remote master. Because, if you are using a project scaffolding tool, like create-app, it creates these files for you, and the remote master needs to be synced with your local before you push.

If you are creating an empty repository on Github, then you can simply push.

answered Jul 7, 2020 at 20:29

As some commented above, the problem could be that you do not have email and username or also in my case the problem was that I was trying to push the branch with a different email in the configuration, to check this:

• git config --list

to modify it (globally):

• git config --global user.email "email@email.com"

answered Apr 24, 2022 at 20:06

I had the same problem, some of the users have answered this. Before push you must have your first commit.
Now for new users I’ve created a series of simple steps. Before that you need to install git and run in command line:

• git config user.email «your email»
• git config user.name «name»

The steps for creating a remote repository (I use dropbox as remote repository):

1. create a directory in Dropbox (or on your remote server)
2. go to the Dropbox dir (remote server dir)
3. type git command: git init --bare
4. on your local drive create your local directory
5. go to local directory
6. type git command: git init
7. add initial files, by typing git command:: git add <filename> 
8. type git command: git commit -a -m "initial version" (if you don't commit you can't do the initial push
9. type git command: git remote add name <path to Dropbox/remote server> 
10. git push name brach (for first commit the branch should be master)

answered Feb 24, 2015 at 8:53