Tower 5.2


Tower is a Git client for OS X that makes using Git easy and more efficient. Users benefit from its elegant and comprehensive interface and a feature set that lets them enjoy the full power of Git.

Tower abstracts Git’s complexity in an easy-to-use interface. For example, lots of actions can be performed simply via drag-and-drop, and mistakes can be undone easily. Advanced users can increase their productivity with features like single line staging, submodule support, or the file history.

  • git-svn support
  • File history
  • git-flow support
  • Submodule support
  • git-lfs support
  • Blame view
  • Single-line staging (per-line committing)
  • Cherry-picking
  • Discard chunks/lines
  • Direct Github, Bitbucket, Gitlab, GitSwarm, Beanstalk, Visual Studio Team Services, Team Foundation Server and Rhodecode integration
  • Support for Bitbucket team accounts
  • Support for full-screen and Retina displays
  • Many powerful drag-and-drop features include merge, rebase, push /pull to/from remote, apply stash, create new branch, etc.

What's New Version 5.2

  • Rebase Onto: Tower now supports the "--onto" flag of the Rebase operation. In a nutshell, this allows you to "switch the base" for a series of commits, which is especially useful for those of you who work extensively with feature branches.
  • Amend Commit: It is now possible to edit a commit without removing the original author’s name using the new Amend Commit option. The resulting commit will still have the original committer as the author and you as the committer.
  • Diff View: The ignore whitespace option will now remain enabled / disabled on file changes.
  • Quick Actions: We’ve improved the sorting of results in the Quick Actions dialog: exact matches now appear at the top of the list.
  • Cherry-Picking: You can now cherry-pick commits that are behind (only available on the remote branch) when viewing the current HEAD branch.
  • Performance: We refactored the initial config loading process, removing potential blocking calls that can result in beachballing.
  • Azure DevOps Pull Requests: In some cases, the URL for Pull Requests was incorrectly generated.