Tower vs SourceTree
When comparing Tower vs SourceTree, the Slant community recommends SourceTree for most people. In the question“What are the best Git clients for Windows?” SourceTree is ranked 10th while Tower is ranked 13th. The most important reason people chose SourceTree is:
In addition to color-coded branches and icons that tell if a file has been added, removed or modified, SourceTree also displays the number of commits that are ahead and behind the remote branch.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Pretty, modern-looking user interface
Tower has a good-looking interface and consists of 3 main views - services, repositories and repository.
Services view for managing integrations with hosting services like GitHub, Bitbucket and Beanstalk.
Repositories view for organizing local and remote repositories into folders and getting general overview about them.
Repo view that consists of two main subviews:
Working copy view shows modified files and their diff and allows wrapping up changes in a commit.
History shows commits alongside metadata and projects file structure.
Additionally, it allows performing various tasks such as merging branches via drag & drop, search allows searching by message, commit hash, author, committer and file and there's a quick open that allows fuzzy-searching for folder names.
Pro Offers a visual way to solve conflicts
Tower shows conflicting files, their authors and the commit that made changes. It then allows selecting which files should be used in the final result.
Pro Github integration
Pro Very polished user interface
Pro Cherry-Picking via drag and drop
Pro Git LFS
Tower comes with built-in support for Git LFS. Handy when working with large files.
Pro Git-flow integration
Git-flow provide a consistent development process by defining a strict branching model that is great for managing large projects. T2 allows setting up and integrating into repos that follow this model.
Pro The UI only shows the needed commands at a time
Tower covers most of the daily tasks that a developer may need to complete. It shows only what you need for the most common tasks without overwhelming the user.
Pro Free for students
If you are a student, you can get your free Tower Pro license here.
Pro Interactive Rebase via Drag and Drop
Pro Undo Support
Many Git actions can be undone in Tower simply by using the keyboard shortcut CMD+Z. Examples: Deleting branches and files, staging changes, rebasing & merging branches, or publishing a branch on a remote
Pro GPG support
Tower offers user profiles. You can then connect GPG keys with your profiles, sign commits and see which commits have been signed and by who.
Pro Informative branch visualization
In addition to color-coded branches and icons that tell if a file has been added, removed or modified, SourceTree also displays the number of commits that are ahead and behind the remote branch.
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 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 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 Simple yet powerful
SourceTree allows you to do advanced Git operations while making them straight-forward for those who are still adjusting to Git.
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.
Pro Built-in integration with Stash and Bitbucket
Sourcetree integrates with repositories hosted on Bitbucket, Stash, GitHub, and Kiln.
Pro Free
Pro Supports Git LFS
Pro Git terminal
Comes with own built-in git terminal independent from other git installations and updated regularly. It's especially good for git beginners who would like to use advanced git functions, but are not ready yet.
Pro Supports Git, Mercurial, and Subversion
Allows managing Git & Mercurial repos side by side. It even allows Subversion interoperability via git-svn or hgsubversion plugins which set up a bridge between either Git and SVN or Mercurial and SVN respectively.
Cons
Con Not free/libre
This application is proprietary, and thus cannot be modified or freely distributed.
Con Expensive
Costs $69 per year!
Con Inefficient UI
In order to not overwhelm the users with information, much of the information is either hidden by default or requires navigating to a different section to access.
Con Doesn't have a built in diff
Con Stability issues on Windows
On a simple repository, the UI often lags or freezes.
Con Doesn't support Subtrees
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 Always slow
Con Requires an account to install and use
Need an Atlassian account to install.
Con Terrible for resolving merge conflicts
It's hard to tell when you are in a conflict state, let alone what to do if it happens.
Con Unstable and terrible UX
The Windows version of SourceTree is riddled with bugs, causing some users to find it unusable.
These include failing to refresh, frequent freezing, and slow performance. The recent redesign (February 2016) has made the UI difficult to navigate.
Con Requires users to be online when starting up
As of 2.3.5, it needs to dial home on every start-up, else it raises alerts to compliance.
Con DEPRECATED -No dark theme
Dark Theme is now available on Windows as well as the MacOS version.
Con Chews CPU
Con The UI of version 2.0+ is so terrible
Tab looks good if you have no more than five repos. If you have a lot, you will know my pain. The source tree will not remember the order of the tab you drag. Everytime you restart the app, it will go back to whatever it likes.
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 2.0.20.1. 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 Browsing folders is troublesome
Choosing files of specific folders for check-in is troublesome.
Con UI is buggy and getting worse with updates
UI elements have been critically broken over the last few updates--interactive rebase for example has been entirely nonfunctional for the last 3 versions--and from the JIRA tickets, it seems UI bugs are not being addressed or triaged.
With the declining stability and lack of QA for this product over the last 2-3years, SourceTree seems a risky choice for teams going forward.
Con Not even possible to change the password
There are tickets about this issue sitting there for years and marked as medium priority. I experienced this since version 1.8. Up until now, there has been no fix. If your company's policy is going to enforce you to change your password, it means you need to remove all the repos and clone them again everytime you change the password. This is the worst ever experience.
Con Varied speeds across different versions
For example, the Windows version is quite slow is comparison to the Mac version.
Con Poor UX for interactive rebase
The interactive rebase window is a pain to use, with poor UX, such as not refreshing the list once a change is made. It's a downgrade from git rebase --interactive
.
Con Not always recognizes changed files
Seems to not always recognize changed files, which means that they will not be pushed to remote origin either. This means if you switch branches, the files will be overwritten and you lose your progress. Very annoying.
Con CRLF on Windows is a nightmare
There is a bug in 'Discard hunk' and 'Discard lines' constantly interrupting the work flow with inserting wrong line endings. Click here for more details.
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.
Con Crashes frequently
Stops responding every 5 minutes.
Con Login problems
Frequently unable to log in, despite the correct password.
Con Uninstalling won't remove the installation completely
If You decide to uninstall, you'll have to manually go to the folder inside the system and directly delete the files. If you uninstalled to reinstall fresh, this is a big issue.
Con Can't select install location
You can't select the install location (anymore). This is terrible for enterprise environments. It insists to install into "Users/<Name>/AppData/Local". What? Where? Why not "Recycle Bin" or Windows Temp?
Con Often rebuilds the graph visually noisy
E.g. after a reset command, the graph disappears and reappears after a few moments.
Con Flawed installer
Enforced registration process doesn't work, shows failure when connected to Bitbucket. Windows are too small to display installation text and options. Installs unwanted icon on the desktop. Slow and unresponsive at times.
Con Blame MS Office's word correction dictionary to be the source of the slowness while it's not
It's so obvious that ever since 2.0, it will try refreshing each of the repo a few minutes. If you have a lot then it will drive you crazy. When you try to expand a branch node, it refreshes. Try again, OOPS, it refreshed again. Sometimes, it will take you five minutes to select the node you want.
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.