Pro Comprehensive layout
SourceTree has three main repository views: file status, history, and search.
File status view shows status of currently selected repo. It's split into two areas - file list and diff-view.
History view tracks changes made to the currently selected repository. It's divided into three sections. The top section has a graph with progression of commits, branches, and merges. The bottom section shows commit details, files changed, and differences committed.
Search view allows looking up commit messages, users, files changes, branches, and commit SHA.
There's also a toolbar at the top that allows switching between the three views, as well as giving access to git commands (such as commit, checkout, reset, stash, add, remove, fetch, pull, push, branch, merge, and tag).
Pro Quick setup
Once installed, SourceTree will automatically try to look for and set up repos that are worked on. SourceTree will also detect if git-flow is used and what is the current development state as long as default git-flow branch names are used.
The software tracks all relevant repositories in the bookmark's window. Repositories can be added to the list by creating new ones, adding a local folder, supplying a clone URL or integrating with remote services such as Bitbucket or GitHub.
Pro Built-in Git-flow and Hg-flow support
Git-flow and Hg-flow provide a consistent development process by defining a strict branching model that is great for managing large projects.
SourceTree allows setting up and integrating into repos that follow this model. Clicking the Git-flow / Hg-flow toolbar button will give you access to actions for starting or finishing features, releases or hotfixes depending on the current state of repository.
Pro Allows chunks and lines selection during commit
SourceTree automatically splits the changes to be committed into chunks allowing committing (or discarding) each chunk separately. Furthermore, the user can even select specific lines. This greatly increases the flexibility of the user in that matter.
Con Can sometimes be slow
Some operations can be slow. If you know what you want (e.g you want to touch a file, add it, commit it, and push it) you can do it much faster on the command line. However you're often not going to know what you want, so the visual diffs (for example) help massively.
Con Does not allow offline installation
Upon installation, the splash screen prompts you to login. There used to be a workaround for you to manually deploy this application in an offline environment, but they've patched it as of 188.8.131.52. It now does a dial-home on each start-up. Since it cannot reach the server, it throws an error to the user, and raises alerts to compliance.
Atlassian's final decision was that they are not going to support this feature at all. Quoted from their staff:
"We’ve never officially supported any form of pre-installation on device management capabilities. [...] As you know, last year, we removed the notion licensing and asked our developers to register the product by creating an Atlassian account. That said, SourceTree has always been a tool for the individual (emphasis mine) developer."
Con Information density can be a bit much
It's possible to become overwhelmed with the information density presented in SourceTree. This is especially the case in history view, as it includes a lot of data presented in various ways.
Though this is great for getting a comprehensive overview of everything that's happening in one place, it can take some getting used to.
Con Has trouble with Github's Yubikey integration
When your 2FA is a hardware key it is difficult to find a way to bring up the ability to use anything but a pre-programmed password function on the Yubikey, which doesn't add much to security all things considered what a hardware key is supposed to do.
Flagged Pros + Cons
Out of Date Pros + Cons
Con Showing diffs of past commits with an external viewer is tricky
For some reason, even though you can easily configure an external diff viewer that works for working copy changes or staging changes, you can't easily use the selected external diff viewer for looking at past commits.
There is a workaround using custom commands, but that is both dumb and doesn't always work.