Src refspec master does not match any ошибка

I have tried to follow the solutions suggested in this post but it didnt work and I am still getting: src refspec master does not match any.

Here is what I did:
Followed this solution

// adding the file I created
$ git add .
$ git commit -m 'initial commit'
$ git push origin master
error: src refspec master does not match any.

When doing:

$ git push origin HEAD:master
b40ffdf..a0d1423  HEAD -> master // looks promising

// adding a remote
$ git remote add devstage -f <another git>
$ git merge devstage/master -s recursive -X ours
$ git push -u devstage master
error: src refspec master does not match any.

More information:

$ git branch 
* origin

$ git show-ref
refs/heads/origin
refs/remotes/devstage/master
refs/remotes/origin/HEAD
refs/remotes/origin/devstage
refs/remotes/origin/master
refs/remotes/origin/origin

So I am definitely missing refs/heads/master but dont know how to create it.

Thanks

The clue is in the error

error: src refspec master does not match any.

Github’s recently changed its default branch to main.
Take a look here

On your local setup you could rename your local branch as shown below

git branch -m master main

or you could push from your master to main

git push origin master:main

answered Oct 23, 2021 at 20:17

In my case the error was caused because I was typing

git push origin master

while I was on the develop branch
try:

git push origin branchname

Hope this helps somebody

answered Jun 17, 2017 at 10:47

This is happend to me once I forgot to add files. So I got the same error. All you need to do is add your files.

1. Add your files => git add . or the name of the files you want to add. you supposed to init first your repo with git init.
2. Commit your changes => git commit -m 'Initial Commit'.
3. Now push your changes => git push -u origin master

answered Feb 3, 2020 at 18:28

answered Sep 12, 2021 at 12:38

Ensure that if you are pushing the master branch then ensure that you’re currently in the master branch if not checkout to the master branch and now push your commits. To list all current branches in your working directory use :

git branch 

Your currently working branch should have an asterisk at the beginning for instance if am working on my a devstage branch it would appears as shown below :

*devstage
master

In this case, push the commits in the devstage branch first then perform a git pull request if you want to merge the two branches that is the master and the devstage.

answered May 31, 2021 at 20:02

answered Mar 19, 2017 at 12:42

This error can typically occur when you have a typo in the branch name.

For example you’re on the branch adminstration and you want to invoke:
git push origin administration.

Notice that you’re on the branch without second i letter: admin(i)stration, that’s why git prevents you from pushing to a different branch!

answered Oct 6, 2017 at 8:42

Setup username and password in the git config

In terminal, type

vi .git/config

edit url with

url = https://username:password@github.com/username/repo.git

type :wq to save

answered Oct 14, 2017 at 13:55

Only because your local branch does not math the one in your remote repository.
git push origin HEAD:master
Enable you to ignore the conflict and upload your commit anyway.

answered Sep 21, 2021 at 15:15

For me, the fix appears to be «git .» (stages all current files). Apparently this is required after a git init?
I followed it by «get reset» (unstages all files) and proceeded with the exact same commands to stage only a few files, which then pushed successfully.

   git . 
   git reset

answered Jun 17, 2017 at 17:01

It happened to me and I discovered that github was trying to verify my account. So you need these 2 commands:

git config --global user.email <your github email>
git config --global user.name <your github username>

answered Nov 30, 2018 at 15:00

FWIW, ran into same error, but believe it came about due to the following sequence of events:

• Remote Git repo was created with master branch.
• Local clone was then created.
• Remote Git repo was then modified to include a dev branch, which was defined as the default branch, in conjunction with permissions added to the master branch preventing changes without a pull request.
• Code updates occurred in the local clone, ready to be pushed to the remote repo.

Then, when attempting to push changes from the local to the remote, received error «src refspec master does not match any», or when attempting to push to dev, «src refspec dev does not match any».

Because changes were pending in the local clone, I did not want to blast it and refresh.
So, fixed the issue by renaming the local branch to dev…

$ git branch -m dev

…followed by the normal push of git push origin dev, which worked this time without throwing the aforementioned error.

answered Sep 4, 2019 at 18:37

This error is also caused due to an unmatched local branch name.
Make sure that you are giving correct local branch name (check spelling and case sensitivity)
I had the same error because my local branch name was «validated» and was trying to push the changes using git push -f origin validate, updated that to git push -f origin validated worked.

Hope this helps.

answered May 2, 2020 at 15:43

I also faced the same error.
In my case below is the scenario.

I have master branch which set as origin.

Other side I have release branch «Release_branch».

I have to fork my feature branch(i.efeature/testBranch) from Release branch.

Below are the steps I did.

$ git checkout Release_branch
$ git pull
$ git checkout feature/testBranch
$ git commit -m "SOME_MESSAGE"
$ git push -u origin feature/testBranch

answered May 4, 2021 at 11:16

I had this error (error: src refspec master does not match any) with a new repository, when trying git push origin master, because GitHub changed the default name of the master branch to main.

So, git push origin main is working for me.

answered May 15, 2021 at 10:46

For a new repository, the method works for me:

1. Remote the files related with git
   rm -rf .git


2. Do the commit again
   git add . && git commit -m "your commit"


3. Add the git URL and try to push again
   git remote add origin <your git URL>


4. And then try to push again
   
   git push -u origin master -f


5. Success!

Since it’s a new repository, so it doesn’t matter for me to remove the git and add it again.

answered Nov 24, 2018 at 22:41

I had already committed the changes and added all the files, had the same origin as remote, still kept getting that error. My simple solution to this was just:

git push

answered Sep 1, 2020 at 20:54

Нет ветки 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)

04 июн. 2023, в 13:43

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

04 июн. 2023, в 13:14

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

04 июн. 2023, в 12:23

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