Tower PRO 17.0-545 Mac

The Undo button alone rewires how you think about Git. Instead of memorizing reset commands and hoping you kept a terminal tab open, you reach for a single toolbar item that walks back the last commit, merge, or rebase without a wall of terminal output. That willingness to treat version control as something you can browse and correct visually runs through the entire app, from the file history viewer that shows every change a project has ever seen to the way branches stack and track across hosting services.

At its core Tower is a native Mac client built by fournova, not a web wrapper dressed in Cocoa. It speaks Git directly and presents the parts developers actually need—staging hunks, resolving conflicts, reviewing pull requests—without burying them in menus. The interface stays in English, and it supports macOS 12 onward on both Intel and Apple Silicon machines.

The PRO tier pushes further into team workflows. Automatic branch management keeps stale branches from piling up after pull requests close, and Fully Merged detection now handles squash and rebase merges, so a branch that looks orphaned locally gets a badge confirming it already landed upstream. Stacked branches let you build a chain of dependent work without juggling long-running feature branches, and the Graphite integration ties into the same pattern for teams already using stacked-review practices.

For self-hosted shops, PRO adds service account creation directly from the app, along with custom workflow scripting and PR merged-branch detection that polls your hosting service rather than guessing from local reflogs. The result is a Git client that still opens fast and looks clean on a laptop screen but carries enough depth for a CI-heavy, multi-repo workday.

Cloning a big repository and immediately pulling every remote branch is the first habit worth breaking. Tower shows you the full branch list right after clone, and the temptation to select all and fetch is strong, but a cleaner start is to let the default branch settle, open the repository, and pull additional remotes only when you need them. The client handles shallow clones just fine, and you spare yourself a cluttered sidebar during the first hour of orientation.

Another early stumble is treating the Working Copy pane as a junk drawer. Beginners often stage everything with a single drag, write a one-word commit message, and move on. The one-line staging view actually invites the opposite: click a file, see exactly which hunks changed, and stage only the chunks that belong together. A commit that mixes a typo fix with a half-built feature is just as hard to untangle in Tower as it is on the command line—the tool simply makes the mistake more visible.

Switch the diff view to side-by-side first

Open Preferences, jump to the General tab, and switch the default diff view from "Unified" to "Side by Side." The split-pane layout makes context switches between old and new code far quicker to scan, especially during code reviews where you move through dozens of files in a sitting. While you are there, check "Show file status in the working copy" so the sidebar includes an icon column—a small change that saves repeated trips to the file list just to see what changed.

Under Git Config, set your default push behavior to "Simple" if it is not already. Tower respects your global Git configuration, but the app ships its own bundled Git binary, and a mismatch between what the terminal uses and what the client uses can cause confusion during a first push. Aligning the two prevents the moment where a terminal git push works and Tower asks for an upstream branch you thought already existed.

For anyone working across services, adding a hosting account right after setup avoids friction later. The PRO edition's Fully Merged detection depends on the connection to your GitHub, GitLab, or self-hosted instance, and the badge that marks a squash-merged branch as done only appears when the app can poll the service. The full tower pro mac full version supports service account creation for self-hosted environments, which means you do not need to leave the app to generate tokens for a CI bot or a team member.

Tower PRO 17.0-545 improves its Fully Merged detection so local branches are matched against pull requests that have already landed via squash or rebase merges—not just traditional merge commits. Previously, a squashed branch often looked unmerged locally; now it receives the badge when the hosting service confirms the PR is closed.

• macOS 12 (Monterey) or later
• Intel or Apple Silicon Mac