After upgrade to Sourcetree 3.2.5 [6 Aug 2019]
There are some differences with before where use push to origin function.
It will auto fill the Remote branch text-box with my new local branch name and can click Push button to push to origin
Sourcetree 3.2.5 [6 Aug 2019]：
It will leave it blank and click Push button will produce error.
This broke for me when upgrading to Sourcetree 3.3.4 on windows. It is a bug in sourcetree.
A workaround for the issue is when sourcetree autofills the "Remote branch" field in the push dialog the first time pushing a new branch from local, Delete what ever sourcestree autofills and enter it manually or copy and past the previous values and the push will work.
I figured out a shorter workaround right after writing this, in the "Remote branch" delete the forwards slash character and the write it again and it will work.
Have not experienced losing any remote branches i only experience the issue with new branches that needs to be pushed remote.
For me, after the first push Source tree cleared the "Remote branch" text box to the empty field. So, push didn't work because "Remote branch" is a simply empty string, but it's hard to track this as it happens at the moment when a dialog box is hidden. Of course, typing a name into "Remote branch" fixes the issue.
Same problem here. If I create a new branch then try to push it to the origin, the remote branch name is left blank and the "Track?" checkbox is left in an indeterminate state.
This results in the following error even after manually entering a branch name and checking the Track? option:
The Remote branch '' (Local branch = 'test2') is invalid. Ref names must follow git ref-format rules:
Completed with errors, see above.
Hello Gerry and welcome to the Community!
Thank you for reporting a change in the product after an update. We would be interested to know what version to upgraded Sourcetree from so we may review the release notes to see if there was a behavior change.
We look forward to hearing back which version you have prior to the upgrade.
I had the same problem as mentioned above.
When upgrading to 3.2.5 from what I think was 3.1.3 (which still works for my colleagues), I could no longer work with the push dialog.
But today, after I've tried to update embedded git (which didn't work), update windows and multiple reboots it works again.
Putting in my 2 cents. For me, it also does not work in 3.2.6 but if I force push, it works. Sometimes the repo admin doesn't make that option available, so I'll try downgrading to 3.1.3.
Still happening in Sourcetree 3.3.4.
@dw-mschneider 's solution worked for me - If the remote branches are blank when trying to Push, which happens when it's a new repository, it used to still work and would create those branches in the remote, but this time I had to enter the branch names manually. Worked after that.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event