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

Push does not work since 3.2.5

Jens-Peter Frank August 13, 2019

I have recently upgraded to version 3.2.5.

Since then Push no longer works. The dialog does not display any branches.

Pull works.


14 answers

10 accepted

13 votes
Answer accepted
Phileo99 September 9, 2019

Based on a suggestion from another user:


I tried upgrading the Embedded Git used by SourceTree  

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

And after that, my Push Dialog showed all the branches once again.


To avoid such problem in the future, SourceTree upgrade process should detect version of Embedded Git and notify user when the Embedded Git also needs to be updated 



However, there still appears to be problems with the Push Dialog:

  • create local branch
  • commit local, do not push to remote branch
  • Open Push Dialog



Push Dialog should show my recent local branch as available to push to remote



Push Dialog does not show my recently created local branch

Jens-Peter Frank September 10, 2019

The change to Git Version Embedded (2.21.0) has helped me.

Like antonio.barreto likes this
valeriuo September 10, 2019

This does indeed seem to work. I suspect even switching to the system git might do the trick.

eyonaian September 10, 2019

@Phileo99  Just tried and it works perfectly! Thanks man.

Like Jens-Peter Frank likes this
Fernando September 11, 2019

It works now! Thanks @Phileo99 

Shira Stein November 5, 2019

"Update Embedded" crashed in the middle so 

I had to do Tools => Options => Git =>Git Version: Embedded

and download the whole thing  (2.21.0) and that solved everything

Like captaincaffeine likes this
P January 16, 2020

Your solution doesn't work in my case and I had to fix downloading the Portable Git 2.21 and replace my version manually.

So If anyone doesn't fix by Source tree could browse the GitFolder and replace the local git version as I did.


5 votes
Answer accepted
markchagers September 11, 2019

In my case upgrading the embedded version of git solved the issue, but I had to switch to actually use the embedded version since I was using the system git at 2.13.1. Updating the system git also worked. So apparently you need to update to git >2.13.1

I can't reproduce the issue reported by @Phileo99 in his update, neither with the embedded git nor the system git. However when I click the local branch to push, it doesn't show the new branch name in the remote branch column like it used to do with earlier versions. The push works however, and after pushing, the name is shown on subsequent pushes.

Fernando September 11, 2019


This fixed the problem for me.

Thanks, @markchagers :)

4 votes
Answer accepted
eyonaian August 14, 2019

I have exactly the same issue. A simple work around to this is by downgrading to an earlier version.

Please Atlassian, can somebody look into this ASAP!

1 vote
Answer accepted
Fernando September 9, 2019

I've got the same problem.

In case this is helpful: I added my repositories to SourceTree by adding existing folders in my HD, not by downloading the code from BitBucket (I already had them synchronized with a previous application)

1 vote
Answer accepted
Jan Drozen August 20, 2019

I created a bug report almost two weeks ago 

Valeriu Ohan September 5, 2019

I can't see the issue page. How is it being handled? Any progress or workaround (beside reverting to an older version)?

valeriuo September 6, 2019

I found some related bug reports:


It looks like the entire push menu doesn't work correctly for some time. Initially, I no longer had auto-completion for remote names of untracked branches (3.2.5). Then, in 3.2.6, this happened.

0 votes
Answer accepted
arumpf September 9, 2019

I have exactly the same issue. This occurred sometime after the automatic update to 3.2.6, although it had been working fine for a few days after the update.

Pushing via the command line still works, and all of my remote branches appear, but no branches show up in the Push window. Fetching does nothing. The same problem affects all of my remote accounts, both on Bitbucket and GitHub.

0 votes
Answer accepted
Phileo99 September 6, 2019

I am experiencing the exact same problem, Push dialog shows empty branches.

Had to downgrade to version 3.1.2 to get back my branches to show in Push dialog.

Atlassian Please FIX, I did not agree to be your unpaid Beta tester !!!

0 votes
Answer accepted
Alexandru Ghitulescu September 6, 2019

I'm really disappointed in SourceTree. Do you guys not do any testing in your release cycle?

0 votes
Answer accepted
Hannes Fischer September 6, 2019

I also have the same issue after updating to the lastest version of sourcetree (v326.3544). Could you please check?

eliacurti September 6, 2019

Same issue. If you try to open "Terminal" and run "git push" it works.

A little workaround.

Like Gasalho Antero likes this
Hannes Fischer September 6, 2019

Thanks for you info, but it doesn't work for me. Using the terminal terminal does not consider my private key. Really strange. After downgrade to v3.1.3 everything is working again, also terminal

Gasalho Antero October 17, 2019


it works for me thanks :).

The issue still remains in Sourcetree

0 votes
Answer accepted
eliacurti September 5, 2019

Same issue! I've recently upgraded to 3.2.6.

How can I solve?

Phileo99 September 6, 2019

you have to downgrade to 3.1.2 or lower

1 vote
the designer January 23, 2021

I've tried most of the fixes here, nothing works; updated SourceTree to the latest version - currently 3.4.2; I'll explain a lot since I'm a noob, so may others can check this fix:

A. As you can see, there are no branches on the right menu; also, the push dialog menu looks like in the picture of the original post;


B. Make sure you are on the local repository, within SourceTree; click Terminal, which opens the command line interface:


In terminal, do the following commands:

$ git status #list the status of git
$ git add <file_name> # Example: git add file_2.txt
$ git commit -m "<msg>" # Example: git commit -m "second file to upload, one more line"
$ git push origin <branch_name> # Example: git push 2021-test-v2 master # aka push to remote repository 2021-test-v2 and brunch master; 

Last command output should be  like:

Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 253 bytes | 253.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
To<your account or username here>/2021-test-v2
* [new branch] master -> master

C. Now you should have the branches shown on the workspace of SourceTree


D. Go on the local repository folder; create a new file, let's say file3.txt;

Go/open again SourceTree, select local repository, see the newly created file3.txt; click on it, choose Stage Selected, write something on the Comment window, click "Commit" button below the comment section. 

E. Go on the left menu/ workspace, see the master branch additional sign and Push button with 1 task waiting;


 F. Make sure you have the last line selected, press Push


G. Now, you should have the possibility to choose the remote repository and branches; 


The Push button will still show 1 task to complete, but the file will be uploaded to the cloud repository; check that by going to account / your repository , master branch or whatever you selected, the file should be there.

Apoorv Singhal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 4, 2021

In your Tools->Options->Git the Push Branches option must not be set to matching in case you want to push an untracked local to remote. Can you check if that was the case for you?

the designer February 5, 2021

Hello, I don't think I have this case; please see the push branches being set to simple.


sschaenzer February 17, 2021

Your post helped me figure out that, if you're upgrading an existing system, all we really need to do is right click on the E. left menu /Workspace branch as you mentioned and push from there! After that the top Push button starts working again!

Vipin Yadav
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 7, 2021

Please provide more info with your settings file, your version, git.config contents, config.json etc. so that we can reproduce it. Also please let us know any other information, which you feel can be useful. 



1 vote
Tony Ladefoged October 7, 2020

Just updated to 3.3.9 and it still doesn't work. Hell, the Terminal menu doesn't work neither (I saw somebody mention this as a work around)

Oleg Denysenko October 12, 2020


0 votes
markchagers February 18, 2021

I think most issues noted here have to do with a disparity between the sourcetree version and the git version in use.

Be aware that sourcetree is nothing but a UI wrapper around git. Some of the issues occurring have nothing to do with sourcetree itself, but with the installed git and it's configuration.

The second thing to be aware of is that sourcetree comes with an embedded version of git but that if you have git installed separately you can also use the 'system version' of git. This setting is available in the git tab of the settings dialog. Here you can also update the embedded git version.

Personally I prefer using the system git, since I have git installed through homebrew, and it gets updated automatically whenever I do a brew update/upgrade, which I do a couple of times a week anyway.

After my initial issues with branches not showing up properly in the push dialog, I could solve these by upgrading the git version in use, and I have never experienced similar issues since (I've used sourcetree extensively both on Windows and on MacOS).

A final thing to be aware of is that sourcetree is a free program and that there is a multitude of similar - free - solutions available (VS Code has excellent git clients, both built in and as extensions for example) so you're not obliged to use sourcetree. If it doesn't work for you find another git client that does.

VladimirV June 11, 2021

I've been fixing this issue either by upgrading git version or by re-installing SourceTree.

But yesterday issue reappeared after update to newer version and now nothing helps.

I'm done with SourceTree. Going to find the replacement (Fork preliminary).

I already suggested to add "Console" window to let users track what ST communicates to git. W/o that it is impossible to guess what goes wrong. Nobody listens. 

0 votes
sschaenzer February 17, 2021

I was also having a problem with the Push since I upgraded to the latest Sourcetree 3.4.2 this morning.

Was about to give up after 3 hours of farting around trying about every solution mentioned here, such as:

I followed the advice from the first post in this thread and upgraded to the latest embedded Git but that didn't fix the issue and now just noticed that I cannot even push from the command line either.

Trying to push from the command line caused a couple of CredentialHelperSelector forms to pop up asking me to select a credential helper: and I have no idea which of the 10 options I want.

Found an article that seemed to say we want the "manager" option.

(I always get a popup credential helper selector as... (

I really am amazed and disgusted that this problem that although was originally reported in Aug 2019, at least 18 months ago, that Atlassian hasn't been able, or hasn't bothered to release a fix for this. There is not even a post here from Atlassian with the definitive answer if there is one.

Nothing worked, the "Push" button at the top never worked right, never showed any branches to push, until AFTER:

I used the right click on the branch and selected the push option I wanted, such as "Push to origin/master (tracked)" which then proceeded to pop a push Dialog with all the possible branches to select from were properly displayed!

Then using the "Push" button there worked except now the CredentialHelperSelector Dialog popped several times where I selected the "manager" option and then the push finally succeeded!

Then after that suddenly the "Push" button at the top started working right! That is it starting showing all the branches that can be pushed as expected instead of none of them. But the CredentialHelperSelector kept popping up until I finally checked the "[ ] Always use this from now on" option there.

This is certainly a Sourcetree bug, that is still in the product. The bug is that whereas Sourcetree knows the branches and they are listed on the panel on the left, the "Push" button at the top fails to discover and present  them in its dialog for the push operation, this is probably a cache problem because once you use a right click Push command from the left panel the top "Push" button starts working again, for all the repo's!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events