Can t push to remote branch cannot be resolved to branch

Question

I migrated my repos from Bitbucket or Github   I don t think this matters but it s the only thing different    For a little while I had two remotes set up   origin  bitbucket github  github   Then I removed both and pointed origin to github   git remote remove origin git remote remove github git remote add origin https   github       Test push of develop branch   git push origin develop   Everything up to date  ok  good   Create a new branch for some work as per usual   git checkout -b Feature Name   Update a file or two   Attempt to push to remote   git push origin Feature Name   This results in the error      fatal  Feature Name cannot be resolved to branch   Search online for this issue  find some stuff about ensuring HEAD is correct  others about making sure I ve got my branch name case correct  though  at this point the branch doesn t exist on the remote yet    Unable to resolve   Ran this command   git push --all -u   This got my Feature Name branch to github  but still see same behavior as prior   git push origin develop git push origin Feature Name   The first works  the second throws the same error   I can t figure out why I m getting this error   Any ideas

User · Answer

A similar thing happened to me  I created a branch called something like  Feat name   I tried to pushed it using       git push --set-upstream origin Feat name   I got the same fatal error as you       fatal  Feat name cannot be resolved to branch   To solve it I created a new branch as I had very few files impacted  Then I listed my branches to delete the wrong one and it displayed with no cap     feat name   I had used caps before but never on the first caracter  It looks like git doesn t like it

User · Answer

I solved this in Windows 10 by using cmd instead of GitBash   It has to do with character case and how git and command lines handles them

User · Answer

Slightly modified answer of  Ty Le   no changes in files were required for me - I had a branch named  Feature      and while pushing upstream I changed the title to  feature       the case of the first letter was changed to the lower one

User · Answer

For my case  I used to have branch folder  or whatever it is called  with capital letters  then I create a new one with difference casing  lowercase  but git actually create the branch with capital   I have created a branch like feature-ABC branch1 before and pushed it  Then I create a branch feature-abc branch2  notice the lower-case ABC   and try to push it to remote using git push --set-upstream origin feature-abc branch2 and get the  cannot be resolved to branch  error  So I git branch and see that it actually created feature-ABC branch2 instead of feature-abc branch1 for me  I checkout again with git checkout feature-ABC feature2 and push it using the uppercase  feature-ABC feature2  to solve it

User · Answer

for me I was naming branch as  Rel4 6 bug Some-short-description  all I had to do is when using  git push origin Relx x bug Some-short-description  to write  git push origin relx x bug Some-short-description  as I used to create branches using small letter r in rel  so  what caused this issue  when I listed  git refs heads content I found drwxr-xr-x  4 eslam khoga  staff   128B Sep 22 20 22 relx x  but no Relx x  and inside it bug and inside bug my branch s name  So  git try to create a dir with same name but different case letters but system is not case sensitive  That s what caused this issue

User · Answer

Had the same problem with different casing    Did a checkout to development  or master  then changed the name  the wrong name  to something else like test     git checkout development git branch -m wrong-name test   then change the name back to the right name   git branch -m test right-name   then checkout to the right-name branch   git checkout right-name   then it worked to push to the remote branch   git push origin right-name

User · Answer

Git will let you checkout the current branch with a different casing  and it will fail to find a ref on the remote   Just found out the hard way

User · Answer

it seems that you try to rename your master branch to Main  by using this command git branch -M Main where you were on master branch  execute this git command  il will work   git push --all -u  after this you can run git branch to see your branches then you can delete the master branch like this   git branch -D master

User · Answer

I ran into the same issue and noticed that I had mixed up the casing while checking out the branch  I checked out branchName instead of BranchName and when I tried to push to remote  I got the same error  The fix  git push --set-upstream origin BranchName  By setting upstream to the correct name  the correct branch was updated on github and I was then able to checkout the correct branch name with git checkout BranchName   And it should be up to date with your last push

User · Answer

If you are in local branch  could rename the branch  Feature Name  to  feature Name   git -m feature Name  if you have problems to make a git push make a checkout in other branch  ex develop  and return to renamed branch  git checkout feature Name  and try again your git push

User · Answer

You might have created similar branch but different case-sensitive-wise  then you have to run   git branch -D  lt name-of-different-case-branch gt   and then try to push again

User · Answer

I was having this issue as well  and it was driving me crazy  I had something like feature name but git branch -a showed me FEATURE name  Renaming the branch  deleting and recreating it  nothing worked  What finally fixed it   Go into  git refs heads  You ll see a FEATURE folder  Rename it to feature

User · Answer

Maybe your forgot to run git fetch  it s required to fetch data from the remote repo  Try running git fetch remote branch

User · Answer

I had the same problem but was resolved  I realized branch name is case sensitive  The main branch in GitHub is  master   while in my gitbash command it s  Master   I renamed Master in local repository to master and it worked

User · Answer

It s case-sensitive  just make sure created branch and push to branch both are in same capital   Example   git checkout -b  TASK-135-hello-world    WRONG way of doing   git push origin task-135-hello-world      FATAL  task-135-hello-world cannot be resolved to branch   CORRECT way of doing   git push origin TASK-135-hello-world

User · Answer

I faced the same issue which was due to going to branch with wrong casing  git let me switch to branch with incorrect casing ie feature Name instead of feature name  Found an easier solution than listed above just    commit your changes to  feature Name  git checkout master  or develop  git checkout feature name  lt  with correct casing git push

User · Answer

I just had this issue as well and my normal branches start with pb-3 1-12345 namebranch but I accidental capitalized the first 2 letters PB-3 1 12345 namebranch  After renaming the branch to use lower case letters I could create the branch

User · Answer

Based on my own testing and the OP s comments  I think at some point they goofed on the casing of the branch name   First  I believe the OP is on a case insensitive operating system like OS X or Windows  Then they did something like this       git checkout -b SQLMigration ReportFixes Switched to a new branch  SQLMigration ReportFixes     git push origin SqlMigration ReportFixes fatal  SqlMigration ReportFixes cannot be resolved to branch    Note the casing difference  Also note the error is very different from if you just typo the name     git push origin SQLMigration ReportFixme error  src refspec SQLMigration ReportFixme does not match any  error  failed to push some refs to  git github com schwern testing123 git    Because Github uses the filesystem to store branch names  it tries to open  git refs heads SqlMigration ReportFixes  Because the filesystem is case insensitive it successfully opens  git refs heads SqlMigration ReportFixes but gets confused when it tries to compare the branch names case-sensitively and they don t match   How they got into a state where the local branch is SQLMigration ReportFixes and the remote branch is SqlMigration ReportFixes I m not sure  I don t believe Github messed with the remote branch name  Simplest explanation is someone else with push access changed the remote branch name  Otherwise  at some point they did something which managed to create the remote with the typo  If they check their shell history  perhaps with history   grep -i sqlmigration reportfixes they might be able to find a command where they mistyped the casing

User · Answer

For me  the issue was I had git and my macOS filesystem set to two different case sensitivities  My Mac was formatted APFS Is Case-Sensitive  NO but I had flipped my git settings at some point trying to get over a weird issue with Xcode image asset naming so git config --global core ignorecase false   By flipping it back aligned the settings and recreating the branch and pushing got me back on track   git config --global core ignorecase true  Credit  https   www hanselman com blog GitIsCasesensitiveAndYourFilesystemMayNotBeWeirdFolderMergingOnWindows aspx

[git] Can't push to remote branch, cannot be resolved to branch

Examples related to git