Hey there -
Just found out about Sourcetree today and was very excited to use it and possibly switch from Tower.app. HOWEVER, I just noticed a huge issue that I can't work around and I'm scratching my head as to whether it's a bug or a "feature".
Basically I have a codebase with a ton of feature and hotfix branches. When I'm working on a particular branch and want to push my changes, I click on the Push button in the toolbar, and instead of getting a dialog like the one the Pull button displays (where the branch i'm working on is selected per context), the dialog shows a list of all branches in my repository -- MOST OF THEM SELECTED!!! -- which means if I'm not careful I would be setting off a nuke and pushing my changes to about 30 different branches rather than just the branch I am working on. Why in the world is SourceTree behaving this way? I even went in and unchecked all branches except the current branch and pushed, but the next time I wanted to push I had to do the same thing over again as all branches were again preselected!!! Very bizarre behavior IMHO and I'm wondering if this is a glaring bug or just a misunderstanding on my part. Perhaps I'm just used to using Tower.app but it doesn't have this NUKE ALL option disguised as a Push button.
I also noticed then even when my branch working copy doesn't have any changes, the Pull button in the toolbar shows that I have 36 changes -- not sure where the "36" is coming from.
It seems that I can get around this by right-clicking on my active branch and selecting "Push to origin/production (tracked)", the branch being "production", but why can't I do this from a button in the toolbar? The Pull button in the toolbar seems to be aware of context.
I'd really like to switch to SourceTree if there was a workaround or way to disable the PUSH TO ALL BRANCHES APOCOLYPSE "feature", but for now it seems to dangerous to use.
Any help would be greatly appreciated.
I will second a request to have a "dedicated push" functionality to the currently checked out branch. Even if current implementation is fully in "sync" with "git push" command, having every time unselect dozens of checkboxes is very user unfriendly. UI should help users with easy way of doing day to day tasks, not blindly follow some "command line" paradigms.
It is not fair comparison between command line and UI applications, as they are using absolutelly different design patterns (e.g. how can I select something in command line ??? why should I type more than required in command line. For example: "git push" makes more sence than "git push all").
The top-level Push dialog default is to behave like a bulk operation, picking up all the branches you've previously configured to push to this remote (not all branches). Pushing to a single branch can either be accomplished using the sidebar (as you discovered), or when committing you can enable the 'Push immediately' option which just pushes the branch you're committing to.
The decision of which branches to select in the Push dialog is entirely down to which branches are configured to push to the given remote. You can see this via 'git remote show <remote>', the section at the bottom labelled "Local refs configured for 'git push':". Only branches which have been pushed to the remote before will have this configured, so when you create new local feature branches for example but don't push those explicitly, they are never selected in the top-level Push dialog. So essentially, the Push toolbar option is a 'Sync' button, where all branches that you've previously decided to push to that remote are selected.
So far, no-one else has raised this as unexpected behaviour in the 18 months we've been out, but I can still see your point of view, especially if other tools Push toolbar buttons pushed just the current branch. Perhaps a Preferences > Git option to flip between the two styles? It would still default to the current behaviour (as I say, no-one's complained about this before so I assume by that that most people are happy with the way it works now), but you could then tailor it to your preference.
Also, the numbers on branches indicate how many commits your branch is ahead/behind the remote branch it is configured to track for pull. You can right-click the branch in the side bar and select 'Track Remote Branch' to see what branch you're tracking, and change it if you want. By default any branch you checked out from a remote will automatically track that remote branch, and the same with any branch you pushed to the remote.
Funnily enough, someone else raised an issue today which indicates the 'git way' of indicating which style of default push you want: https://jira.atlassian.com/browse/SRCTREE-1019 - this would be the best way to implement this I think. Sadly, this git configuration setting is not reflected in the output of 'git remote show' - if it was SourceTree would automatically do it.
Thanks for the response, Steve. That clarifies things a lot, though I have to admit I'm still puzzled by the implementation. Maybe it's because I'm just used to the UI paradigm that Tower.app uses. So if I understand you correctly, you're saying that the Push button in the toolbar, when clicked, shows a sheet containing all branches along with a checked checkbox if that branch is set for tracking, and then when I cick "OK" in the sheet, I won't be pushing my current branch to all the selected branches, but instead each tracked branch will push from their local branch to remote branch? In other words, the current branch working copy is not relevant?
If this is the case, then yes, this is behaving like a "Sync" button. And while you guys hit a home run on developing this unique feature, I think you struck out on the naming ;)
If I could make a suggestion, I'd suggest renaming the current "Push" button in the toolbar to "Sync" and retain its current unique functionality. Then I'd add a new button "Push" that behaves much like the "Pull" button in that it only acts on the current branch by default.
Actually SourceTree simply mirrors the default behaviour of 'git push' without any parameters, if you haven't changed the configuration setting 'push.default' from it's initial setting, which is 'matching'. Git treats 'tracking' to mean on Pull, not Push by default. git push will push any matching branches on the remote. Therefore the naming convention is entirely consistent with the default git behaviour - the fact that Tower behaves as if 'push.default' is always set to 'current' (which is not the default git configuration) is a personal choice ;)
I plan to support alternate push.default settings in future, but as it stands the default Push behaviour is entirely consistent with git's own default behaviour when invoked with no context (other than the repo itself).
Just found this.
Yes, I am annoyed by this default behavior. In previous version actually (two months ago?), only my current branch is selected when I click on "push" - instead of now, every branch is selected! So annoyingly dangerous. Maybe in previous 18 month no one raised the issue, because it doesn't select all like the current version?
184.108.40.206 is the latest and that should definitely be using ~/Library/Preferences/com.torusknot.SourceTreeNotMAS.plist (sorry, forgot the .plist in my last post). I just did a quick test here changing a setting and that file is definitely the preferences file getting updated with 220.127.116.11.
This push all feature is completely unintuitive and downright dangerous.
As a first time user of sourcetree I got really screwed over by this.
I've never before pushed "all branches" in my life and I don't think the majority of git users have either.
Now I have to train myself to right click my branch and push from there and never ever push the giant button in the toolbar with the word PUSH on it.
Hi Everyone! My name is Mina and I am on Atlassian’s Ecosystems Marketing team. Our team is focused on our technology partnerships and marketplace apps. One of Atlassian’s partners is Slack, who ...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events