Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


After upgrading to Sourcetree 3.2.6 the push dialog doesn't show the available branches to push

This is happening on a colleague's machine. I can still push to the remote via the command line but not via the SourceTree push dialog. We tried restarting Sourcetree and also restarting the laptop (running Windows 10 x64). I'm running the same version of SourceTree (3.2.6) on my machine without any problems (same OS). Any ideas how to trouble shoot this?

6 answers

1 accepted

0 votes
Answer accepted
Mike Corsaro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 09, 2019

Hello! Your colleague might not be on the same version -- there was an issue with this in v3.2.5. You can manually download 3.2.6 here, or open Options > Updates and check for the new update which is now available to all users.


As a workaround if you're not able to upgrade: uncheck and then check the "push" checkbox in the push dialog for the empty entry you're attempting to push and it should work. Sorry about that!

Thanks for your reply Mike. When I go to the "Help -> About" in SourceTree on my colleague's laptop it tells me that version 3.2.6 is running.

And to clarify: his push dialog box has no entries at all even though he has multiple local branches (both local only and remote tracking branches), so your workaround isn't applicable. He just uses git push via the command line.

On my machine (with the same 3.2.6 version) I get my local branches listed and the remote tracking branch name (if they exist) or just a blank remote branch name for local only branches.

Mike Corsaro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 09, 2019

I suspect something odd is happening.

Can you have your colleague do the following:

  • Open "Tools > Options > Git"
  • Try checking the "Disable LibGit2 integration" checkbox and see if that changes anything


If that doesn't fix it, then try and do the following:

  • Open the process viewer -> "Tools > Process Viewer"
  • Open the push dialog
  • Observe the command run when the dialog is opened:
    • Find the entry for "push" (GetBranchesForPush is the caller context) and view the process output. It should list the result

From there, you should be able to run the same command and see if the output is the same.

Like # people like this

Thanks for your help Mike. It turned out that my colleague had an older version of git (2.11.0) and that one didn't know the format option to the git branch command so instead of the list of branches on the remote, we got an error message. I believe the --format option to git branch was introduced with git 2.13.0. After we upgraded his system to git version 2.23.0 it all started to work again.

Like # people like this

I have same problem and this answer solve it.

I have older version git (2.13.0) When I update new version it work

Thanks you.

We had the same problem.

The Git version that was running was 2.13.3

Upgraded to the latest Git version and issue was fixed.


Like Oleksandr Bodashko likes this

Solved for me after switching from System to Embedded GIT which I updated to v2.21

Like Alexander Oss likes this

The check and uncheck did the trick for the error I was just experiencing.  I was getting the following when I tried to push to a new remote on GitLab in v 3.2.6Screen Shot 12-02-19 at 07.28 PM.PNG

Like Natalia Pascual likes this

Guys I tried two things after I upgraded to version 2.3.6

a) First of all get the latest GIT

Remember to update both the versions if your system is a 64 bit machine, I observed that even the default 64 bit was downloaded, the system option still referred the 32 bit which was older 

Git for Windows Setup

32-bit Git for Windows Setup.

64-bit Git for Windows Setup.

Once i updated the git exes to point to the latest , at least the big annoying issue of empty Push dialog got solved

$ git --version
git version


b) There was another nagging issue, if you have created a fresh local branch and tried to push to remote, it wont show in the push dialog 

You have to make sure the push branches is NOT set to matching value, the default or the upstream value solved this 



Changing push branches from current to upstream seems to have done the trick. Thank you

I've been facing this issue for months but still can't figure it out.  Like Manohar described, I create a fresh local branch, then try to push my changes so I can submit a PR with that branch.  However, I never see my new branch in the Push dialog.  I tried EVERY SINGLE "Push Branches" option there is.  The behavior is exactly the same, regardless of what I set.  I've just been using command-line to push to my changes.

I have changed the Tool -> option -> git -> push branches simple to upstream it's worked for me. Thank you!!

I have changed the Tool -> option -> git -> push branches simple to upstream it's worked for me too. Thank you!!

thank you man !! it works :D 

3 votes

Hi, I'm having the same issue with Source Tree 3.2.6: newly created local branches cannot be pushed because they do not appear in push dialog, I need to use command line and it's highly annoying.

Updating system Git to version 2.23.0 didn't fix it.

If I try to update embedded version, it downloads Git 2.21.0 and that doesn't solve the problem either.

Slightly different from the issue we had.  Someone could have 5 or 10 local branches and none of them would show up in the Push dialog. The "Branches to push" list was completely empty.    They all appear now that the system Git has been upgraded.

The same for me.

I have the same issue, any luck getting it solved?

Downloading the embedded git version solved the issue for me (Tools->Options->Git->Git version->Updated Embedded).

Like # people like this

Same issue here.  Process Log shows all branches in the output, but new branches are not visible on Push UI Dialog, only old branches.   Tried upgrading embedded git and with and without Lib2Git enabled.

Running command in terminal shows all branches.

Only difference between new and old branches are new branches do not have a remote name.  After manually pushing, new branches still do not have a remote name, and still do not appear

Deleting local branch and pulling remote causes new branch to appear in push dialog, so I may have missed an option when pushing for the local to track remote after push. 

Check (Tools -> Options -> Git -> Push branches), if it is set to 'matching', you would get the behavior your are describing).

Like # people like this

Thanks, changing that setting does adjust the branches that appear in the pull dialog.   It really should only adjust the items that are checked by default.  Seems to be a change in behavior (or a change in default settings)  between versions.   Some of the options filter the pull dialog, others only affect with is checked by default, they provide a mix of different types, but nothing like the previous behavior for matching. 

It may be an issue with how the branches are created, as old local-only branches are showing correctly. 

using simple now shows all 3 types  (old remote tracked, old local, new local), 

Like Janice Vann likes this

Changing (Tools -> Options -> Git -> Push branches) from matching to simple worked for me as well.

Same here, downloading the embedded git version solved the issue for me as well.

Tools->Options->Git->Git version->Updated Embedded.

Thanks! Updated Git + Git embed worked for me on 3.2.6

GIT UPDATE solved this for me :)

Hi, I had same problem, but after (re)downloading the embedded Git version and restart, the problem was solved.

I had the same problem after upgrading. I followed the most of the above steps, to no avail. In the end I saw Tools->Options->Git->Git Version->Emedded was not activated.

I Selected it so that it became greyed out. Now it worksAnnotation 2019-12-25 181031.jpg

Thanks @andreodendaal

That also fixed the problem for me!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events