SourceTree 1.5: Going with the Flow
By Steve on July 17, 2012Steve Streeting has made it his mission to reach out to SourceTree users and listen to what they have to say. In the last couple months, he’s even traveled to San Francisco from his hometown in the UK, hosting a drinkup to meet SourceTree customers face to face. He’s taken your feedback and pushed out some of the features you’ve asked for in the latest release – SourceTree 1.5!
What’s New?
Git-flow and Hg-flow Support
A development model first published by nvie, Git-flow (and its Mercurial equivalent – Hg-flow) organizes your repositories by formalizing the use of feature branches, releases, and hot-fixes. SourceTree 1.5 now lets you adopt this model, so you can unclutter your repository and develop stress-free.
Reverse Granular Changes from Previous Commits
Sometimes, you need to revert a change that you made, but undoing an entire commit can be painful. Whether you want to reverse a change made in a line, a chunk of code, or an entire file, SourceTree 1.5 now gives you that power. Highlight the changes you want to reverse and click reverse. Take complete control over your code — the way it should be.
Bitbucket Teams Support
Bitbucket Teams let you create a shared account in Bitbucket to consolidate your team-owned repositories and organize your group’s work. SourceTree now gives you options to configure Teams settings when you create a hosted repository. Easily collaborate on code using SourceTree and Bitbucket.
A Whole Lot More
In addition to bug fixes, we’ve added a couple more of the features you’ve asked for. To name a few:
- Added support for default push options other than ‘matching branches’. You can change this in Preferences now to other defaults (e.g. ‘current’).
- Added global preference to disable fast-forward merges, takes effect on context menu merges too
- Support dragging & dropping bookmarks to other apps (passing the repository paths)
- Support creating a branch at a commit other than HEAD for Git repositories
- And a whole lot more! To check out the rest, read through our release notes
Give the new release a try! Download it for free today!
11 Comments
Steve, thanks a lot for implementing the Reverse Granular Changes support – it’s so great to see how easy it is to suggest a new feature 😉
Keep up the good work!
The download server asks for a password. 🙁
Hmm, it seems to be working fine here, no password prompt. The link should be to http://sourcetreeapp.com/download. Can you try again please?
https://downloads.atlassian.com/software/sourcetree/SourceTree_1.5.0.dmg still asks for a password.
I’ve just tested this from a Mac I’ve never used before (so no chance I have any cached credentials) and I get no password prompt. Are you sure this isn’t something on your network that’s blocking the download?
Very strange, Chrome shows a modal http auth dialog while Safari starts the download as expected…
Hi Steve!
I don’t seem to find a feature request button, so I’ll just post it here.
Perhaps it is a good idea to include Notification Center support for Mountain Lion, so one gets a notification when a new repository has been updated/changed.
Thanks for the suggestion – we had this on the list for a while under ‘Growl’ but it didn’t reach the top of the list, now of course Mountain Lion changes that a bit. It would be nice to support both but we’ll have to see. For future reference you can request features at https://jira.atlassian.com
Hi Steve!
I like the Git-flow feature! But I would like to see the merge of a feature into the develop branche be a –no-ff merge, like it is written in Vincent Driessen’s branching model. (also for release finishing release and hotfix branches) This cannot be solved by disabling ff merges globally in my opinion..
Keep up the good work!
Hmm, I just use the default behaviour of git-flow’s ‘feature finish’ here (as written by Mr Driessen ;)) which does set –no-ff automatically. The only time it doesn’t do this is if there have been no commits on the feature branch when you finish the feature.
Remember, back in the early day of the Internet, there was a popular response in forums, RTFM? Here’s my message to you, Atlassian folks: WTFM. Cheers.