Sourcetree Push dialog does not show any branches

[Phileo99]

Git Pull dialog works fine.

However when I press the Push button, the Push dialog shows me an empty list of branches when I am expecting a list of branches available to push

[Vincent Rozendaal · Accepted solution]

In my case it was caused by an older version of git (prior to 2.13.0) not understanding the format option to git branch command. Upgrading to Git 2.23.0 solved the problem.

[Michael Evenson]

I am running 3.2.6 and have the same issue. Steps:

1. created repository on bitbucket.org.
2. cloned repository to local machine to an empty folder
3. copied files into the newly created folder where the .git directory was created
4. using SourceTree, staged all of the files
5. entered commit comment and clicked the commit button (lower right)
6. tried to Push commited files

Result - the push dialog with no branches listed and just a blue spinny for-ever.

[Phileo99]

Try this solution, it worked for me (at least partially):

https://community.atlassian.com/t5/Sourcetree-questions/Push-does-not-work-since-3-2-5/qaq-p/1152545#M31058

[Michael Evenson]

This worked for me:

I tried upgrading the Embedded Git used by SourceTree  

(Tools => Options => Git => Update Embedded Git)

Thanks for the link

[Michael Evenson]

But now I get this error when I try to push:

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags --set-upstream <repository-name> master:master
Pushing to bitbucket.org/<my-name>
fatal: 'bitbucket.org/<my-name>' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Completed with errors, see above.

where <repository-name is the name of the repository I am trying to commit to and <my-name> is the name added to the bitbucket url . Both exist at bitbucket.org.

[mlmathews]

I've tried both system git (updated to 2.23) and embedded git (2.21) and neither solved the problem for me. I'm having the problem with both ssh and file system origin repos.

[mlmathews]

I discovered a way to "fix" the problem that is probably also a clue for the bug.

If I set my new branch to track an existing remote branch (doesn't matter which branch) then immediately change it back to track "None", it then shows up in the push dialog.

[Deleted user]

You're right, I have the same issue and upgrading Git didn't work, but the trick of tracking/untracking branches did it! Thanks a lot!

[Janice Vann]

The trick of tracking/untracking branches worked for me also.

[fgregoire]

The trick of tracking/untracking branches worked for me also.

[Phileo99]

It looks like Atlassian has made a new release of SourceTree:
https://product-downloads.atlassian.com/software/sourcetree/windows/ga/ReleaseNotes_3.3.4.html

Has anyone tested whether it fixes this problem of first time local branch not showing in Push Dialog?

https://community.atlassian.com/t5/Sourcetree-questions/Push-does-not-work-since-3-2-5/qaq-p/1152545?utm_source=atlcomm

[Deleted user]

I'd like to try it out, but can't find how to download version 3.3.4 of SourceTree.

[mlmathews]

3.3.4 doesn't seem to be officially released...yet.

[eaespinoza0]

This solution worked for me.

[Andreas Diktyopoulos]

[SOLUTION - setting the merge property in .git/config file]

For me, nothing else worked. So I get into the .git/config file:

The problem there was that the branches didn't have the merge property at all. It was like that:

[branch "feature/labels"]
   remote = origin
[branch "feature/interaction-tools"]
   remote = origin

The solution was to set the merge property:

[branch "feature/labels"]
   remote = origin
   merge = refs/heads/feature/labels
[branch "feature/interaction-tools"]
   remote = origin
   merge = refs/heads/feature/interaction-tools

[Michal Plesnivy]

For me, this setting works (Embeded Git 2.30.2, SourceTree  3.4.4):

[Nathasya S]

this worked for me. Thank you so much

[Matthew Back]

This also worked for me. Thanks :)

[Inge Prefontaine]

This worked for me, thank you.

[Martin Schneider]

(Tools => Options => Git => Update Embedded Git)

I did this in SourceTree 3.4.16. Embedded Git version was about 2.6 then 2.37.
Now I get several Git errors and SSH agent isn't working either anymore.
Reinstalling SourceTree did not solve anything yet. Now my SourceTree is completely destroyed 😑.

Edit:
After the reinstall of SourceTree I did "Update Embedded Git" again and then clicked on "Embedded". Now everything works.

[Theepranai.sos]

I tried in tool option and then it worked for me.

[sajico]

This solution worked for me also.

My "System" Git installed by "Docker Toolbox" was "git version 2.9.0.windows.1".

Thanks for capture!

[Michael Meier]

Same problem here, and this solution worked for me too!

[William Leslie]

Thanks!  Selecting system made it work.

[troy_meyer]

Selecting the "Update Embedded" in the Tools > Options > Git dialogue worked for me.

[Happy Dhingra]

Thanks. Solution worked for me too!!

[DreamMasterXXL]

Yes solved the issue. Thanks

[Justin RH Payne]

Selecting Embedded and restarting SourceTree worked for me. Thank you.

[Holly_Yelland]

This worked for me, thanks!

[GibranSimplix]

Worked for me too!!!! many thanks!!

[陈晨]

Worked for me ~ Thanks~

[Jens GEBHARDT]

selected Embedded and it works again, thanks. 

[rvanderplas]

Thanks! Works for me as well. 

[Jaye Jiang]

Worked for me, thanks.

[sonny]

Updating SourceTree or the embedded git didn't solve this issue for me.

Instead, I followed Jason Paulson's comment in a related thread:

- Check (Tools -> Options -> Git -> Push branches)

- Change this setting from "matching" to "simple"

- EDIT: If this setting was already on "simple", try switching it to "matching" (and then back to "simple" if you want)

[mlmathews]

Yay!...this is the real solution (at least for me).

Here's a little additional information on this issue that I discovered:

The underlying issue is that when using the "matching" setting, the SourceTree push dialog only displays branches that have [branch] entries in the .gitconfig file. My previous solution of manually setting and unsetting the remote tracking branch works because it's causing an .gitconfig entry for the branch to be created.

[Lijun Wang]

My issue is when I tried to push the second time(the first time the branch showed up and I was able to push), the branch was not listed. So I updated embedded git, did not work. Then I changed Tools->Options->Git->Push branches from simple to matching. The local branch showed up. 

[Yi Han]

I had a similar problem, but changing simple(which was the default setting) to matching worked for me! XD

[Gary_Stanton]

I tried a bunch of the suggestions here, but this is the one that worked for me - although, I changed the setting from 'simple' to mixed. I suspect therefore that the setting itself isn't the issue, but changing it triggers some kind of refresh.

[chamodt]

I followed the way mentioned by Yi Han it worked for me.

[J. Ryan Jones]

This was the way that solved it for me, also.

[crazie developer]

I have tried:

- Check (Tools -> Options -> Git -> Push branches)

- Change this setting from "matching" to "simple"

- Disabling LibHit2 integration

Didn't work.

- Updated git to 2.30 (having Sourcetree 3.4.3)

That worked, for a time. Now I realized I had git problem which was solved by bash command from local git repo:

git push --set-upstream origin master

(or any other branch name)

[johnOrmerod]

I had recently updated SourceTree to 3.3.8. I found this problem of local branches to be pushed dialog being  empty. I followed the suggestioon to upgrade Git. I went from 2.12.2 to the latest version, which is 2.25.1. Closed STree and Git. Re-opened both and now STree displays all available branches.

I'm happy.

[tonoslav]

GIT UPDATE solved this for me :)

[Lijun Wang]

You can also right click the branch and select "track remote branch"->"origin/master", then the push button will have number appeared and when you click the push button, your branch will be in the list. 

[Marcelo Vellame]

Same issue here, I just:

• closed Sourcetree;
• updated GIT;
• reopened Sourcetree and viola!

[九木旭]

我通过更新git修复了这个问题

git 2.11=>Git-2.29.2.3-64-bit

我的版本是 SourceTreeSetup-3.3.9

感谢大家

[Vladimir Tormoz]

For me, the problem was that the local and the remote branch names didn't match! I simply renamed my local branch (named it exactly the same as remote one) and my local branch magically appeared in the list.

[Sih-Ying_Wu]

had the same issue here on windows, switch git to embedded version works for me. 

[Karl Hansen]

I branched local/[mybranch-didnotpush] to local/[mybranch-thiswillpush], and and pushed local/[mybranch-thiswillpush] to origin/[mybranch-didnotpush].  Then I deleted local/[mybranch-didnotpush], and renamed local/[mybranch-thiswillpush] to local/[mybranch-didnotpush].  Now local/[mybranch-didnotpush] does push.