Ошибка гит src refspec master does not match any

I clone my repository with:

git clone ssh://xxxxx/xx.git

But after I change some files and add and commit them, I want to push them to the server:

git add xxx.php
git commit -m "TEST"
git push origin master

But the 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'

aloisdg

22k6 gold badges84 silver badges102 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!

ChrisB

1,4306 silver badges19 bronze badges

answered Sep 27, 2011 at 16:07

baisongbaisong

56.6k1 gold badge14 silver badges7 bronze badges

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

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).

answered Nov 15, 2010 at 11:24

Vi.Vi.

36.6k18 gold badges91 silver badges148 bronze badges

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.

answered Jan 4, 2012 at 17:03

AryoAryo

4,3292 gold badges28 silver badges24 bronze badges

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.

answered Aug 9, 2017 at 9:22

VIKAS KOHLIVIKAS KOHLI

8,0844 gold badges50 silver badges59 bronze badges

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

grg

4,8143 gold badges32 silver badges49 bronze badges

answered Sep 2, 2014 at 1:56

pyforkpyfork

3,6872 gold badges20 silver badges18 bronze badges

I found this happened in a brand new repository after I Git added only a directory.

As soon as I added a file (e.g. a README), Git push worked great.

answered Sep 25, 2011 at 1:44

Andrew EAndrew E

7,5993 gold badges41 silver badges38 bronze badges

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

answered Nov 3, 2012 at 20:30

aug2uagaug2uag

3,3693 gold badges30 silver badges53 bronze badges

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

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

Werner

2,5371 gold badge26 silver badges38 bronze badges

answered Jan 12, 2015 at 17:30

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'

tanius

13.4k3 gold badges51 silver badges62 bronze badges

answered May 23, 2012 at 17:43

wilsonfozwilsonfoz

8578 silver badges9 bronze badges

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

Jin KwonJin Kwon

19.9k14 gold badges109 silver badges179 bronze badges

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

answered Jun 14, 2021 at 7:28

Make sure you’ve added first, and then commit/ push:

Like:

git init
git add .
git commit -m "message"
git remote add origin "github.com/your_repo.git"
git push -u origin master

answered Apr 28, 2018 at 7:12

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

answered Dec 16, 2020 at 18:47

Two possibilities:

1- Either you forgot to include the .gitignore file.

Here are all the steps required:

Create an empty Git repository on remote,
On local, create the .gitignore
file for your project. GitHub gives you a list of examples here

Launch a terminal, and in your project do the following commands:

git remote add origin YOUR/ORIGIN.git

git add .

git commit -m "initial commit or whatever message for first commit"

git push -u origin master

2- Or you are trying to create a new GitHub project.

GitHub replaced master with main as the default branch name. To resolve the issue:

On your local project:
1. remove the .git folder if it exists
2. recreate a clean repository by launching the following in your project:

In the terminal:

git init

git add .

git commit -m "YOUR FIRST MESSAGE HERE"

git branch -M main

git remote add origin _GIT_LINK_TO_PROJECT_HERE_

git push -u origin main

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.

answered Jan 13, 2020 at 6:01

AreehaAreeha

8237 silver badges11 bronze badges

You probably forgot the command git add . after the git init command.

Lucas

5242 gold badges10 silver badges19 bronze badges

answered Apr 25, 2019 at 14:37

SumerSumer

2,65923 silver badges24 bronze badges

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

Do it like this way…

Create a repository on GitHub
Delete existing .git file in your local directory
Go to the local project directory and type git init
git add .
git commit -m"My first commit"
Now check your branch name. It will be master in your local project
git remote add origin <remote repository URL past here from the GitHub repository>, and then type git remote -v
git push -f origin master
Now check the GitHub repository. You will see two branch 1. main 2. master
In your local repository create a new branch and the branch name will be main
git checkout main
git merge master
git pull origin main
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 Oct 9, 2020 at 16:17

iamtheasadiamtheasad

98711 silver badges15 bronze badges

Just add an initial commit. Follow these steps:

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

This worked for me.

answered Dec 28, 2017 at 7:02

NeeruKSinghNeeruKSingh

1,5453 gold badges21 silver badges26 bronze badges

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

Henry Ecker♦

34.1k18 gold badges38 silver badges56 bronze badges

answered Feb 28, 2021 at 12:20

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

AnthonyAnthony

13.2k13 gold badges59 silver badges79 bronze badges

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.

answered Jun 2, 2021 at 11:01

AlaminAlamin

1,80913 silver badges32 bronze badges

Maybe the branch is main instead of master.

Try

git push origin HEAD:main

git push origin main

answered May 20, 2021 at 18:21

This happens when you have added your file, forgot to commit and pushing.
So commit the files and then push.

answered Dec 3, 2011 at 13:29

user993563user993563

18.3k10 gold badges42 silver badges55 bronze badges

First, git add .
Second, git commit -m "message"
Third, git push origin branch

Please check for spelling mistakes because that could also give that error.

answered Jun 11, 2015 at 14:15

If you get this error while working in detached HEAD mode, you can do this:

git push origin HEAD:remote-branch-name

See also: Making a Git push from a detached head

If you are on a different local branch than the remote branch, you can do this:

git push origin local-branch-name:remote-branch-name

answered Mar 2, 2018 at 14:36

snapsnap

1,5111 gold badge14 silver badges20 bronze badges

It happens if you forget to commit before pushing for the first time. Just run:

git commit -m "first commit"

answered Sep 8, 2019 at 9:56

Badr BellajBadr Bellaj

11.4k2 gold badges42 silver badges44 bronze badges

To check the current status, git status.

And follow these steps as well:

git init
git add .
git commit -m "message"
git remote add origin "github.com/your_repo.git"
git push -u origin master

answered Sep 12, 2019 at 7:48

DinithDinith

78913 silver badges22 bronze badges

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

xurixuri

8307 silver badges18 bronze badges

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 Feb 11, 2017 at 21:49

neoDevneoDev

2,8693 gold badges33 silver badges66 bronze badges

I also followed GitHub’s directions as follows below, but I still faced this same error as mentioned by the OP:

git init
git add .
git commit -m "message"
git remote add origin "github.com/your_repo.git"
git push -u origin master

For me, and I hope this helps some, I was pushing a large file (1.58 GB on disk) on my MacOS. While copy pasting the suggested line of codes above, I was not waiting for my processor to actually finish the add . process. So When I typed git commit -m "message" it basically did not reference any files and has not completed whatever it needs to do to successfully commit my code to GitHub.

The proof of this is when I typed git status usually I get green fonts for the files added. But everything was red. As if it was not added at all.

So I redid the steps. I typed git add . and waited for the files to finish being added. Then I followed through the next steps.

answered Mar 22, 2019 at 16:16

GelGel

2,8262 gold badges17 silver badges25 bronze badges

Источник

Я создал новый проект с одним файлом README.md.
И сделал команду

git clone https://github.com/xxxx/xxx.git
git add .
git commit -m "v.01"
git push origin master

Но получаю ошибку

error: src refspec master does not match any
error: failed to push some refs to https://github.com/xxxx/xxx.git

Я вводил
git show-ref

3deeeb53dda70bea0809cff5e4032011ba45ac7d refs/heads/main
27383695f3f76e87254687449d73250254560bbb refs/remotes/origin/HEAD
27383695f3f76e87254687449d73250254560bbb refs/remotes/origin/main
3deeeb53dda70bea0809cff5e4032011ba45ac7d refs/remotes/origin/master

И делал так

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

mkdir repo && cd repo
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 master

Success!

Я пытался еще так
git push origin HEAD:master
Но хоть загрузка и произошла но файлы не загрузились в github

Но это не помогло что мне делать как исправить

Вопрос задан

более двух лет назад
23441 просмотр

Нет ветки master, вот и ругается. Ветка по умолчанию на GitHub теперь называется main.

Команда git branch -vv покажет какие ветки есть локально и с какими внешними ветками связаны.
* main 0e02250 [origin/main] v.01

Надо было делать git push origin main
Либо просто git push т. е. отправить текущую ветку в связанную с ней ветку на внешнем репозитории.
В нашем случае текущая ветка main (помеченная звёздочкой)
отслеживает исходную ветку main в репозитории обозначенном как origin

Что скрывается за сокращением origin покажет команда git remote -v

origin	https://github.com/xxx/xxx.git (fetch)
origin	https://github.com/xxx/xxx.git (push)

Пригласить эксперта

Ввожу git branch -vv — никакого ответа
git push -u origin main не работает хотя связь с удаленным репозиторием установлена

работает так
Для отправки в удаленный репозиторий
git push origin master:master

Показать ещё
Загружается…

13 июн. 2023, в 20:23

5000 руб./за проект

13 июн. 2023, в 20:17

3000 руб./за проект

13 июн. 2023, в 19:27

4000 руб./за проект

Минуточку внимания

Источник

When working with Git, you may come across an error that says «src refspace master does not match any».

Here’s what the error means and how you can solve it.

You may get this error when you try to trigger a push from a local repository to a master repository like this:

git push origin master

This error can occur for different reasons.

The most likely reason this error will occur is that the master branch does not exist.

Perhaps you cloned a new repository and the default branch is main, so there’s no master branch when you try to push for it.

You can display the remote branches connected to a local repository using the git branch -b command like this:

git branch -b

# results
#  origin/main
#  origin/feat/authentication
#  origin/other branches ...

With the above results, you can see that there is no master repository (origin/master). So when you try to push to that repository, you will get the «respec error».

This result also applies to any other branch that does not exist. Let’s say, for example, I make changes and push to a remote hello branch that does not exist:

git add .
git commit -m "new changes"
git push origin hello

This command will produce the following error:

error: src refspec hello does not match any

How to Fix the «src refspec master does not match any» Error

Now you are aware that the master branch does not exist. The solution to this error is to either create a local and remote master branch that you can push the commit to or to push the commit to an existing branch – maybe main.

You can create a remote master branch on a Git managed website (like GitHub) or you can do that directly from your terminal like this:

git checkout -b master

# add commit

git push origin master

These commands will create a master branch locally. And by pushing to origin master, the master branch will also be created remotely.

But if you do not want to create a master branch, you can use the existing default branch (which may be main) instead.

Wrapping up

So if you get the Error: src refspec master does not match any error when you try to push to master, the most viable reason is that the master branch does not exist.

Learn to code for free. freeCodeCamp’s open source curriculum has helped more than 40,000 people get jobs as developers. Get started

Источник

Table of Contents
Hide

When does git throws error: src refspec master does not match any?
1. Scenario 1 – Pushing the changes to master or remote branch
2. Solution for error: src refspec master does not match any.
3. Scenario 2 – Check if a remote branch exists.
4. Scenario 3 – Mismatch in Local and remote branch
5. Scenario 4 – Committing and pushing Empty Directory in Git

There are quite a few reasons Git throws an error: src refspec master does not match any. Let us look at each of these cases and the solution to it.

Scenario 1 – Pushing the changes to master or remote branch

Let’s say you have created a git repository and added all the files from your local branch, but before committing the files, you try to push them into the remote branch or master branch.

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

After adding the files from the local branch, if you do git push, you will get an error: src refspec master does not match any. error: failed to push some refs to master.

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

Solution for error: src refspec master does not match any.

All you need to perform is git commit with a proper message and then do git push to the remote origin to avoid any errors.

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

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

Scenario 2 – Check if a remote branch exists.

If you are working with Github, they have replaced the master branch with the main branch. Hence, in these circumstances, the local branch and remote branch ref will differ, and when you try to push the changes, git will throw an error since the remote branch itself is not present.

Solution – First, check what refs you have, and once you find that, make a git push to the specific remote branch.

# To get all the ref 
git show-ref

# replace with your branch name according to ref 
git push origin HEAD:<branch>

Scenario 3 – Mismatch in Local and remote branch

Generally, even the typo in the branch name while pushing the commit to the remote branch will lead to a refspec error.

Solution – Validate and check if you have given the right branch name while pushing the code to the remote branch.

Scenario 4 – Committing and pushing Empty Directory in Git

A certain version of Git like GitHub, bitbucket does not track the empty directories, so if a directory is empty and you are trying to commit and push, it will lead to an error: src refspec master does not match any.

Solution – Add a file to your directory before pushing it to a remote branch.

Avatar Of Srinivas Ramakrishna

Srinivas Ramakrishna is a Solution Architect and has 14+ Years of Experience in the Software Industry. He has published many articles on Medium, Hackernoon, dev.to and solved many problems in StackOverflow. He has core expertise in various technologies such as Microsoft .NET Core, Python, Node.JS, JavaScript, Cloud (Azure), RDBMS (MSSQL), React, Powershell, etc.

Sign Up for Our Newsletters

Subscribe to get notified of the latest articles. We will never spam you. Be a part of our ever-growing community.

By checking this box, you confirm that you have read and are agreeing to our terms of use regarding the storage of the data submitted through this form.

Источник

You need to add a file to a commit before you can push your changes to a remote Git repository. If you create a new repository and forget to add a file to a commit, you may encounter the “src refspec master does not match any” error.

In this guide, we discuss what this error means and why it is raised. We walk through an example of this error so you can figure out how to fix it on your computer.

Supplement

Problem faced

Commands used before the problem

My mistake

My solution

Feb, 2022 Update:

Минуточку внимания

How to Fix the «src refspec master does not match any» Error

Wrapping up

Table of Contents
Hide

Scenario 1 – Pushing the changes to master or remote branch

Solution for error: src refspec master does not match any.

Scenario 2 – Check if a remote branch exists.

Scenario 3 – Mismatch in Local and remote branch

Scenario 4 – Committing and pushing Empty Directory in Git

Sign Up for Our Newsletters

Sign Up for Our Newsletters

Find Your Bootcamp Match

src refspec master does not match any

An Example Scenario

The Solution

Conclusion

Возможно, вам также будет интересно:

Supplement

Problem faced

Commands used before the problem

My mistake

My solution

Feb, 2022 Update:

Минуточку внимания

How to Fix the «src refspec master does not match any» Error

Wrapping up

Table of Contents Hide

Scenario 1 – Pushing the changes to master or remote branch

Solution for error: src refspec master does not match any.

Scenario 2 – Check if a remote branch exists.

Scenario 3 – Mismatch in Local and remote branch

Scenario 4 – Committing and pushing Empty Directory in Git

Sign Up for Our Newsletters

Sign Up for Our Newsletters

Find Your Bootcamp Match

src refspec master does not match any

An Example Scenario

The Solution

Conclusion

Возможно, вам также будет интересно:

Table of Contents
Hide