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
asked Jan 21, 2014 at 17:13
special0nespecial0ne
6,09317 gold badges67 silver badges107 bronze badges
4
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
3
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
apprenticeDevapprenticeDev
8,0293 gold badges23 silver badges25 bronze badges
5
Try to do :
git push origin HEAD:master
answered Nov 29, 2017 at 14:53
1
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
2
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
Bourbia BrahimBourbia Brahim
14.5k4 gold badges39 silver badges52 bronze badges
0
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
SaikatSaikat
14.3k20 gold badges104 silver badges126 bronze badges
0
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
2
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
pcodexpcodex
1,83215 silver badges17 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
SonuSonu
7129 silver badges7 bronze badges
0
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
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
zhyd1997zhyd1997
1453 silver badges15 bronze badges
1
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.
- Add your files =>
git add .or the name of the files you want to add. you supposed to init first your repo withgit init. - Commit your changes =>
git commit -m 'Initial Commit'. - Now push your changes =>
git push -u origin master
answered Feb 3, 2020 at 18:28
DINA TAKLITDINA TAKLIT
7,11410 gold badges70 silver badges75 bronze badges
this error occurs when you clone a repo from one branch and you trying to push changes to another branch just try to make sure that you are in the same branch compared to the branch that you are trying to push if it isnot the same just clone your repo again from that specific branch by using git clone -b <branchname> <remote-repo-url> then retry to push changes
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
stanley mbotestanley mbote
9561 gold badge7 silver badges17 bronze badges
Check that you call the git commands from the desired directory (where the files are placed).
answered Mar 19, 2017 at 12:42
NoamGNoamG
1379 bronze badges
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
Prashanth SamsPrashanth Sams
19.8k20 gold badges102 silver badges125 bronze badges
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 Jan 19, 2018 at 1:44
0
I had the same problem recently. but now resolved this issue. Because, Now GitHub changed master to main. It works well for me. Use git push origin main instead of git push origin master. Hopefully, It will work.
answered Sep 21, 2021 at 15:15
Vintage CoderVintage Coder
4411 gold badge6 silver badges9 bronze badges
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
JohnP2JohnP2
1,89919 silver badges17 bronze badges
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
jessjess
237 bronze badges
FWIW, ran into same error, but believe it came about due to the following sequence of events:
- Remote Git repo was created with
masterbranch. - Local clone was then created.
- Remote Git repo was then modified to include a
devbranch, which was defined as the default branch, in conjunction with permissions added to themasterbranch 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
TrentiumTrentium
3,4292 gold badges12 silver badges19 bronze badges
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
RupeshRupesh
8501 gold badge12 silver badges26 bronze badges
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
rahulnikharerahulnikhare
1,3601 gold badge18 silver badges25 bronze badges
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:
-
Remote the files related with git
rm -rf .git
-
Do the commit again
git add . && git commit -m "your commit"
-
Add the git URL and try to push again
git remote add origin <your git URL>
-
And then try to push again
git push -u origin master -f
-
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
backslash112backslash112
2,1051 gold badge24 silver badges29 bronze badges
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
Vivek SinghVivek Singh
3563 silver badges14 bronze badges
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
asked Jan 21, 2014 at 17:13
special0nespecial0ne
6,09317 gold badges67 silver badges107 bronze badges
4
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
3
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
apprenticeDevapprenticeDev
8,0293 gold badges23 silver badges25 bronze badges
5
Try to do :
git push origin HEAD:master
answered Nov 29, 2017 at 14:53
1
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
2
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
Bourbia BrahimBourbia Brahim
14.5k4 gold badges39 silver badges52 bronze badges
0
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
SaikatSaikat
14.3k20 gold badges104 silver badges126 bronze badges
0
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
2
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
pcodexpcodex
1,83215 silver badges17 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
SonuSonu
7129 silver badges7 bronze badges
0
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
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
zhyd1997zhyd1997
1453 silver badges15 bronze badges
1
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.
- Add your files =>
git add .or the name of the files you want to add. you supposed to init first your repo withgit init. - Commit your changes =>
git commit -m 'Initial Commit'. - Now push your changes =>
git push -u origin master
answered Feb 3, 2020 at 18:28
DINA TAKLITDINA TAKLIT
7,11410 gold badges70 silver badges75 bronze badges
this error occurs when you clone a repo from one branch and you trying to push changes to another branch just try to make sure that you are in the same branch compared to the branch that you are trying to push if it isnot the same just clone your repo again from that specific branch by using git clone -b <branchname> <remote-repo-url> then retry to push changes
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
stanley mbotestanley mbote
9561 gold badge7 silver badges17 bronze badges
Check that you call the git commands from the desired directory (where the files are placed).
answered Mar 19, 2017 at 12:42
NoamGNoamG
1379 bronze badges
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
Prashanth SamsPrashanth Sams
19.8k20 gold badges102 silver badges125 bronze badges
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 Jan 19, 2018 at 1:44
0
I had the same problem recently. but now resolved this issue. Because, Now GitHub changed master to main. It works well for me. Use git push origin main instead of git push origin master. Hopefully, It will work.
answered Sep 21, 2021 at 15:15
Vintage CoderVintage Coder
4411 gold badge6 silver badges9 bronze badges
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
JohnP2JohnP2
1,89919 silver badges17 bronze badges
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
jessjess
237 bronze badges
FWIW, ran into same error, but believe it came about due to the following sequence of events:
- Remote Git repo was created with
masterbranch. - Local clone was then created.
- Remote Git repo was then modified to include a
devbranch, which was defined as the default branch, in conjunction with permissions added to themasterbranch 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
TrentiumTrentium
3,4292 gold badges12 silver badges19 bronze badges
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
RupeshRupesh
8501 gold badge12 silver badges26 bronze badges
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
rahulnikharerahulnikhare
1,3601 gold badge18 silver badges25 bronze badges
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:
-
Remote the files related with git
rm -rf .git
-
Do the commit again
git add . && git commit -m "your commit"
-
Add the git URL and try to push again
git remote add origin <your git URL>
-
And then try to push again
git push -u origin master -f
-
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
backslash112backslash112
2,1051 gold badge24 silver badges29 bronze badges
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
Vivek SinghVivek Singh
3563 silver badges14 bronze badges
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
Я создал новый проект с одним файлом 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 masterSuccess!
Я пытался еще так
git push origin HEAD:master
Но хоть загрузка и произошла но файлы не загрузились в github
Но это не помогло что мне делать как исправить
-
Вопрос задан
-
26980 просмотров
Нет ветки 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
-
Показать ещё
Загружается…
21 сент. 2023, в 20:40
20000 руб./за проект
21 сент. 2023, в 20:29
2000 руб./за проект
21 сент. 2023, в 19:28
10000 руб./за проект
Минуточку внимания
Ad
At Career Karma, our mission is to empower users to make confident decisions by providing a trustworthy and free directory of bootcamps and career resources. We believe in transparency and want to ensure that our users are aware of how we generate revenue to support our platform.
Career Karma recieves compensation from our bootcamp partners who are thoroughly vetted before being featured on our website. This commission is reinvested into growing the community to provide coaching at zero cost to their members.
It is important to note that our partnership agreements have no influence on our reviews, recommendations, or the rankings of the programs and services we feature. We remain committed to delivering objective and unbiased information to our users.
In our bootcamp directory, reviews are purely user-generated, based on the experiences and feedback shared by individuals who have attended the bootcamps. We believe that user-generated reviews offer valuable insights and diverse perspectives, helping our users make informed decisions about their educational and career journeys.
Find the right bootcamp for you
X
By continuing you agree to our
Terms of Service and Privacy Policy, and you consent to
receive offers and opportunities from Career Karma by telephone, text message, and email.
