Git ошибка error src refspec master does not match any

asked Jan 21, 2014 at 17:13

This should help you

git init
git add .
git commit -m 'Initial Commit'
git push -u origin master

answered Nov 26, 2015 at 5:42

From git branch it appears that somehow your local branch name is «origin».

You can rename the branch with -mv flag, like this:

git branch -mv origin master

After this git branch should show master

Just to make sure the name is indeed the only thing that went astray, you can run git log and look at the last few commits — and compare them to the last few commits on bitbucket website.

answered Jan 21, 2014 at 19:29

Try to do :

git push origin HEAD:master

answered Nov 29, 2017 at 14:53

i have same problem, to solve it, follow these steps

 git init
 git add .
 git commit -m 'message'
 git push -u origin master    

after this, if you still having that error, follow these steps again

 git add .
 git commit -m 'message'
 git push -u origin master 

that worked for me and Hope it will help anyone

answered Mar 4, 2017 at 16:51

By just adding an empty commit will fix issue by using

$ git commit -m "empty commit" --allow-empty
$ git push

above. make empty commit without edit then push

answered Jan 12, 2019 at 10:40

Try following command:

git push origin HEAD:master

Git threw the below error when I tried simply git push. So clearly this is because Git matches the local and remote branch while pushing commits. This is the push.default behavior, you can find out more details here.

fatal: The upstream branch of your current branch does not match
the name of your current branch.  To push to the upstream branch
on the remote, use

    git push origin HEAD:<Branch_Name>

To push to the branch of the same name on the remote, use

    git push origin <Branch_Name>

To choose either option permanently, see push.default in 'git help config'.

answered Apr 10, 2018 at 7:03

I was having the SAME ERROR AGAIN AND AGAIN.

I added files in local repository and Trying the command

«git push origin master»

Showed Same Error

ALL I WAS MISSING I DID NOT COMMIT .

» git commit -m ‘message’ «

After Runnig this it worked

answered Mar 2, 2018 at 17:28

pcodexpcodex

1,79215 silver badges16 bronze badges

Run the command git show-ref, the result refs/heads/YOURBRANCHNAME
If your branch is not there, then you need to switch the branch by

git checkout -b "YOURBRANCHNAME"

git show-ref, will now show your branch reference.

Now you can do the operations on your branch.

answered Jul 6, 2017 at 7:08

The error demo:

007@WIN10-711082301 MINGW64 /d/1 (dev)
$ git add --all

007@WIN10-711082301 MINGW64 /d/1 (dev)
$ git status
On branch dev
Initial commit
Changes to be committed:
  (use "git rm --cached <file>..." to unstage)

    new file:   index.html
    new file:   photo.jpg
    new file:   style.css

007@WIN10-711082301 MINGW64 /d/1 (dev)
$ git push origin dev
error: src refspec dev does not match any.
error: failed to push some refs to 'git@github.com:yourRepo.git'

You maybe not to do $ git commit -m "discription".

Solution:

007@WIN10-711082301 MINGW64 /d/1 (dev)
$ git commit -m "discription"
[dev (root-commit) 0950617] discription
 3 files changed, 148 insertions(+)
 create mode 100644 index.html
 create mode 100644 photo.jpg
 create mode 100644 style.css

007@WIN10-711082301 MINGW64 /d/1 (dev)
$ git push origin dev
To git@github.com:Tom007Cheung/Rookie-s-Resume.git
 ! [rejected]        dev -> dev (fetch first)
error: failed to push some refs to 'git@github.com:yourRepo.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

answered Dec 17, 2017 at 15:36

DINA TAKLITDINA TAKLIT

6,80110 gold badges69 silver badges73 bronze badges

stanley mbotestanley mbote

9001 gold badge7 silver badges17 bronze badges

NoamGNoamG

1379 bronze badges

Prashanth SamsPrashanth Sams

19.3k20 gold badges101 silver badges125 bronze badges

answered Jan 19, 2018 at 1:44

Vintage CoderVintage Coder

4311 gold badge6 silver badges9 bronze badges

JohnP2JohnP2

1,88919 silver badges17 bronze badges

jessjess

237 bronze badges

TrentiumTrentium

3,3892 gold badges12 silver badges19 bronze badges

RupeshRupesh

8301 gold badge12 silver badges26 bronze badges

rahulnikharerahulnikhare

1,3621 gold badge18 silver badges25 bronze badges

backslash112backslash112

2,0751 gold badge23 silver badges29 bronze badges

Vivek SinghVivek Singh

3263 silver badges14 bronze badges

asked Nov 15, 2010 at 6:09

Maybe you just need to commit. I ran into this when I did:

mkdir repo && cd repo
git init
git remote add origin /path/to/origin.git
git add .

Oops! Never committed!

git push -u origin master
error: src refspec master does not match any.

All I had to do was:

git commit -m "initial commit"
git push origin main

Success!

1. Try git show-ref to see what refs you have. Is there a refs/heads/master?

Due to the recent «Replacing master with main in GitHub» action, you may notice that there is a refs/heads/main. As a result, the following command may change from git push origin HEAD:master to git push origin HEAD:main

1. You can try git push origin HEAD:master as a more local-reference-independent solution. This explicitly states that you want to push the local ref HEAD to the remote ref master (see the git-push refspec documentation).

I also had a similar error after deleting all files on my local computer, and I have to clean up all files in the repository.

My error message was something like this:

error: src refspec master does not match any.
error: failed to push some refs to 'git@github ... .git'

And it was solved by executing the following commands:

touch README
git add README

git add (all other files)
git commit -m 'reinitialized files'
git push origin master --force  # <- caution, --force can delete others work.

git push -u origin master
error: src refspec master does not match any.

For that you need to enter the commit message as follows and then push the code:

git commit -m "initial commit"

git push origin master

Successfully pushed to master.

For me I had to make sure the public key is properly configured on the server (appended in ~/.ssh/authorized_keys) and in GitHub/Bitbucket (added to my SSH keys on GitHub or Bitbucket) — they need to match. Then:

git add --all :/
git commit -am 'message'
git push -u origin master

This happened to me in a brand new repository after I ran git add with only an empty directory.

As soon as I added a file (e.g. a git add README.md), then git push worked great.

answered Sep 25, 2011 at 1:44

Missing or skipping git add . or git commit may cause this error:

git push -u origin master
Username for 'https://github.com': yourusername
Password for 'https://yourusername@github.com': 
error: src refspec master does not match any.
error: failed to push some refs to 'https://github.com/yourusername/foobar.git'

To fix it, reinitialize and follow the proper sequence:

git init
git add .
git commit -m 'message'
git *create remote
git push -u origin master

To fix it, re-initialize and follow the proper code sequence:

git init
git add .
git commit -m 'message'
git push -u origin master

This happens too when you are in a specific branch and try to push another branch that does not exist yet, like:

$ git branch
* version-x  # you are in this branch
  version-y

$ git push -u origin master
error: src refspec master does not match any.
error: failed to push some refs to 'origin_address'

I faced the same problem, and I used --allow-empty:

$ git commit -m "initial commit" --allow-empty
...
$ git push
...

Supplement

One of main reasons of this problem is that some Git servers, such as BitBucket, don’t have their master branch initialized when a fresh repository is cloned.

answered Oct 25, 2018 at 1:33

Problem faced

I had the same problem when I was creating a new repository on GitHub and linking it with my React app in the client computer I have.

I used the following steps:

Commands used before the problem

git init
git commit -m "first commit"
git branch -M main
git remote add origin "_git repository link here_"
git push -u origin main

My mistake

But as you can see, my mistake was not using the git add . command.
I did this mistake, because I already had the README.md file and GitHub instructs us with basic commands while creating the repository.

My solution

My solution is to use git add . after the git init command.

Use the following set of commands in the same order to overcome the problem:

git init
git add .
git commit -m "first commit"
git branch -M main
git remote add origin "_git repository link here_"
git push -u origin main

I faced the same issue some days ago.

If you created a new repository nowadays (2020) then the default branch is main on GitHub.

You can check on GitHub now in your repository branches.

And you can also check the branch in the terminal by running the command:

git branch

So that’s why you need to run

git push origin main

instead of

git push origin master

For me,following worked to move untracked files:

git add --all

Next, I followed similar steps

 git commit -m "First commit"

Then,

git remote add origin git@github.....

Last but not the least:

git push -u origin master

As you do this, Windows security will pop up asking for your username and password.

After the GitHub update 2000-10-01, you should use main instead of master.

Do it like this way…

1. Create a repository on GitHub
2. Delete existing .git file in your local directory
3. Go to the local project directory and type git init
4. git add .
5. git commit -m"My first commit"
6. Now check your branch name. It will be master in your local project
7. git remote add origin <remote repository URL past here from the GitHub repository>, and then type git remote -v
8. git push -f origin master
9. Now check the GitHub repository. You will see two branch 1. main 2. master
10. In your local repository create a new branch and the branch name will be main
11. git checkout main
12. git merge master
13. git pull origin main
14. git push -f origin main

Note: from 2020-10-01, GitHub decided use main instead of master branch to use as the default branch name.

answered Dec 28, 2017 at 7:02

Feb, 2022 Update:

If your branch is «main»:

Run this command:

git push origin main

If your branch is «master»:

Run this command:

git push origin master

My issue was that the ‘master’ branch hadn’t been created locally yet.

A quick

git checkout -b "master"

created the master branch, at which point, a quick

git push -u origin master

pushed the work up to the Git repository.

answered Dec 12, 2014 at 19:38

I have faced the same issue, and this solved my problem:

Just make a branch:

git checkout -b "master"

After that,

git push -u origin master

Boom.

Maybe the branch is main instead of master.

Try

git push origin HEAD:main

or

git push origin main

answered Dec 3, 2011 at 13:29

answered Jun 11, 2015 at 14:15

answered Mar 2, 2018 at 14:36

answered Sep 8, 2019 at 9:56

answered Sep 12, 2019 at 7:48

This just mean you forgot to do the initial commit, try

git add .
git commit -m 'initial commit'
git push origin master

answered May 4, 2014 at 14:18

I had the same problem when I missed to run:

git add .

(You must have at least one file, or you will get the error again.)

answered Mar 22, 2019 at 16:16