SourceTree

SourceTree for Mac 1.7 – Now Available!

By on September 16, 2013

The most recent update to SourceTree for Mac is now available, and includes a ton of great new features to make your life easier.

download_button_mac

Create pull requests via SourceTree

We wanted to make it easier than ever to create pull requests straight from SourceTree, so now you can! Simply click on the menu item (Repository > Create pull request) and away you go.

creating a pull request

Signing

A simple new interface allows you to sign your commits or tags in Git and Mercurial. Simply enable signing, select your key, then choose when you want to sign a commit or tag.

Enable GPG signing

Command output history

Wondering what you just did, or want to learn more about the commands that are issued? You can now see all the commands that were issued while that repository window was open.

Command history

Incoming/outgoing full diff

In Mercurial you can now see all the changes you’re going to pull, before you pull them. This makes it easier to see what changes you’re going to incorporate. We’ve also reduced the amount of data that gets pulled by up to 100 percent!

Incoming full diff - hg

Improved search in hosted repositories

You can now search on any field in the hosted repositories screen, making it easier than ever to quickly find what you’re looking for.

Hosted repositories

Plus many, many other improvements

download_button_mac


Got questions, concerns, comments? We’d love to hear from you! Grab us on Twitter @sourcetree.

12 Comments

  • Marius Landwehr
    Posted September 16, 2013 at 5:12 am | Permalink

    With which kind of services are supported for the pull request feature?

    • Anonymous
      Posted September 16, 2013 at 6:23 am | Permalink

      Bitbucket, Stash and GitHub. BB and GH should work straight out of the box, and Stash will work if you already have a Stash account configured in Hosted Repositories. Otherwise, edit your remote via Settings and complete the ‘enhanced integration’ section in the lower half of the dialog.

  • Joakim Berglund
    Posted September 16, 2013 at 5:29 am | Permalink

    Awesome update!

  • Steve Curtis
    Posted September 16, 2013 at 5:51 am | Permalink

    I just upgraded to this version and committed some changes but when I go to Push the changes it says “No changes to push”. Anybody else having this problem?

    • Anonymous
      Posted September 16, 2013 at 6:24 am | Permalink

      I assume this is Mercurial? I can’t replicate that here, the change in this release for hg is that you get to preview the incoming / outgoing changes in full instead of just as text, but this works for all my hg repos here.

      • Steve Curtis
        Posted September 16, 2013 at 7:10 am | Permalink

        Yes it’s Mercurial. I fixed it. I had cleared my browsing history which wiped out user/passwords for Mercurial. Once I logged into my repository via the browser and saved user/password SourceTree worked fine. Thanks for responding.

      • Steve
        Posted September 20, 2013 at 8:00 am | Permalink

        Looks like the new 1.7.1 update fixed my issue. Thanks!

  • Marc-A Bouchard
    Posted September 16, 2013 at 7:10 am | Permalink

    Great update ! I would like to know when squash commit are scheduled ?

  • Mike Bailey
    Posted September 16, 2013 at 9:39 am | Permalink

    Update looks great. Got excited when seeing better Cmd+F support, but see it didn’t address SRCTREE-1294 yet. Hoping to see Find support in the Blame window soon. Thanks for the great work!

One Trackback

  • By Michael Tsai - Blog - SourceTree 1.7 on September 17, 2013 at 11:50 am

    […] Atlassian has released a new version of its SourceTree client for Git and Mercurial. I use it in concert with Tower. Tower has a cleaner user interface that’s great for committing changes and viewing the contents of a commit, including multiple files at once. SourceTree, though, has a better per-file history view and can search the contents of a commit rather than just the comments. (This search feature seems to be broken for me in the current version; I’m currently talking with their tech support people about it.) […]