Right-click your local branch in the sidebar on the left, then select Track Remote Branch, and then the remote branch you want it to track. That will then be the default when you push next time.
I did as what you said, the default pull branch changed, but default push branch didn't change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In that case you probably need to change your settings in Tools > Options > Git, the 'Push branches' option should be set to 'upstream'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, that's a bug. 'Upstream' should pre-select that branch, I re-produced it here and will fix.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just needed to allow SourceTree permission to change my GIT configuration (global tab) and the problem goes away
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm still seeing this issue. It has been over two years, when can we expect a fix?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes this is still an issue. In the right-click menu for the branch, the correct tracked remote is shown. If you click this menu item, the correct remote is pre-selected in the push branches dialogue. However, if you use the keyboard shortcut for push (command-shift-P in my case) when it opens the push branches dialogue, it pre-selects 'origin' even though the only branch ticked is one branch set to track a different remote. It feels like if you could skip the push dialogue (which I'd like to do as it's pointless anyway), it would work. Or if there was a keyboard shorcut for that right-click menu, it would also work as you could just hit enter to OK the push branches dialogue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, "Tools > Options > Git, the 'Push branches' option should be set to 'upstream'" helped me!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This bug still exists in Sourcetree 2.1, but you can work around it by renaming your preferred push branch to "origin", and then secret sourcetree magic will allow that branch to be the default push branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This bug still exists in 2020 version 3.2.1 (Mac), along with many other Sourcetree bugs. Sourcetree feels like abandonware.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also having this issue. I set "pushe Branches" to Upstream on the settings, but if I use the push button on the top I need to check the branch where I want to push.
Why is not setting the current branch as default? I am missing something?
@ekloecker2 did you found a fix?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.