Tower Pro: Exclusive Features

1. Overview

Tower Pro is the set of exclusive features available only on the Pro ($129/user/yr) and Enterprise ($149/user/yr) plans. These features go beyond Tower's core Git GUI capabilities and target professional development teams and complex workflows. Tower Pro currently includes six exclusive feature areas, each with its own dedicated page.

2. Stacked Branches

Canonical: https://www.git-tower.com/pro/stacked-branches

Stacked branches (also called stacked PRs or stacked diffs) is a modern development workflow where a large feature is broken into a series of small, dependent branches — each building on the previous one. Rather than one large PR that is slow to review and blocks other work, stacking produces a sequence of focused PRs that can be reviewed and merged incrementally.

What Stacked Branches Solves

• Large PR problem: a single large PR is slow to review, creates conflicts, and blocks parallel work. Stacking produces small, reviewable PRs that can be merged independently.
• Review velocity: reviewers can review and merge stacked PRs while development continues on dependent branches.
• Conflict reduction: working close to main reduces the number and severity of merge conflicts.

Tower's Stacked Branch Capabilities (Pro)

• Visual stacking view showing the hierarchy of stacked branches and their associated PRs
• Automatic restacking when a parent branch changes
• Submit pending changes to a PR in the stack
• Merge a branch and its parent branches into the base branch
• Fold a stacked branch into any of its parent branches
• Rearrange or merge branches in the stack
• Undo stacking operations with Cmd+Z

3. Graphite Workflow

Canonical: https://www.git-tower.com/pro/graphite-workflow

Graphite is a popular stacked PR workflow platform used by engineering teams at companies including Meta, Figma, and Notion. Tower Pro integrates the Graphite workflow natively, so stacks can be created, restacked, and submitted without using the Graphite CLI.

The Graphite integration allows Tower Pro users to manage Graphite-tracked stacks directly from the Tower UI, including syncing with Graphite's remote tracking of stack state, creating Graphite PRs, and keeping stacks in sync as branches evolve.

4. Advanced Custom Workflows

Canonical: https://www.git-tower.com/pro/advanced-custom-workflows

Tower Pro's Advanced Custom Workflows allow users to create, save, and run sequences of Git commands and Tower actions as named workflows — accessible via a keyboard shortcut, the Quick Actions palette, or a toolbar button. A workflow can combine multiple steps (fetch, rebase, push, open PR) into a single click, enforcing team conventions and eliminating repetitive multi-step procedures.

• Create workflows from sequences of any Git commands, shell scripts, or Tower actions
• Assign keyboard shortcuts to workflows for instant execution
• Share workflows across a team via Tower's configuration files
• Built-in workflow library with common patterns as starting points

5. Automatic Branch Management

Canonical: https://www.git-tower.com/pro/automatic-branch-management

As projects grow, local repositories accumulate stale branches — branches that have been merged but not deleted, or work-in-progress branches from weeks ago. Automatic Branch Management (available in Tower Pro) detects branches that have been merged into the default branch (including merges that happened through PRs on GitHub/GitLab/Bitbucket) and offers to clean them up automatically.

• Automatically detect merged local and remote branches
• Detect branches merged via PR on hosting platforms (requires PR-Based Merge Detection)
• Configurable cleanup: archive, delete, or ignore detected stale branches
• Keep branch lists manageable on large, long-running projects

6. Self-Hosted Repositories

Canonical: https://www.git-tower.com/pro/enterprise-services

Tower Basic supports pull request management for cloud-hosted services (GitHub.com, GitLab.com, Bitbucket.org, Azure DevOps). Tower Pro adds pull request management for self-hosted and on-premises instances of these same platforms:

• GitHub Enterprise Server (self-hosted)
• GitLab (self-hosted)
• Azure DevOps Server (on-premises)
• Bitbucket Server / Data Center

Requires Pro or Enterprise plan. Configured in Tower's Services Manager by entering the server URL and authentication credentials.

7. PR-Based Merge Detection

Canonical: https://www.git-tower.com/pro/pr-merged-detection

When a PR is merged on GitHub, GitLab, or Bitbucket, Git itself has no awareness that a merge occurred through the PR interface rather than a local command. Tower Pro's PR-Based Merge Detection solves this by querying the connected hosting service to detect when a branch's PR has been merged, even if no local Git operation was performed.

This powers Automatic Branch Management: Tower Pro can automatically identify and offer to clean up branches whose PRs have been merged on the hosting platform, keeping local repository state in sync with the remote.