Alternatives to SourceTree logo

Alternatives to SourceTree

GitKraken, Bitbucket, Tower, GitHub, and Fork are the most popular alternatives and competitors to SourceTree.
10.4K
7.9K
+ 1
727

What is SourceTree and what are its top alternatives?

Use the full capability of Git and Mercurial in the SourceTree desktop app. Manage all your repositories, hosted or local, through SourceTree's simple interface.
SourceTree is a tool in the Source Code Management Desktop Apps category of a tech stack.

Top Alternatives to SourceTree

  • GitKraken
    GitKraken

    The downright luxurious Git client for Windows, Mac and Linux. Cross-platform, 100% standalone, and free. ...

  • Bitbucket
    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

  • Tower
    Tower

    Use all of Git's powerful feature set - in a GUI that makes you more productive. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • Fork
    Fork

    Manage your repositories without leaving the application. Organize the repositores into categories. Fork's Diff Viewer provides a clear view to spot the changes in your source code quickly. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • Sublime Merge
    Sublime Merge

    A snappy UI, three-way merge tool, side-by-side diffs, syntax highlighting, and more. Evaluate for free – no account, tracking, or time limits. ...

  • SmartGit
    SmartGit

    It is a graphical Git client with support for SVN and Pull Requests for GitHub and Bitbucket. It runs on Windows, macOS and Linux. ...

SourceTree alternatives & related posts

GitKraken logo

GitKraken

731
909
279
Git GUI Client for Windows Mac and Linux built on Electron
731
909
+ 1
279
PROS OF GITKRAKEN
  • 59
    Dark theme
  • 34
    Best linux git client
  • 29
    Great overview
  • 21
    Full featured client
  • 20
    Gitflow support
  • 19
    Beautiful UI
  • 18
    Very easy to use
  • 16
    Graph
  • 13
    Works great on both linux and windows
  • 13
    Effortless
  • 6
    Easy Merge Conflict Tool
  • 5
    Amazing Github and Bitbucket integration
  • 4
    Great UX
  • 3
    Integration with GitHub
  • 3
    Automatic Repo Discovery
  • 3
    Submodule support
  • 3
    Easy to Learn and Setup
  • 3
    Super fast
  • 2
    Fuzzy find (CTRL P)
  • 1
    Very user friendly
  • 1
    Much more stable than source tree
  • 1
    Great for non-dev users
  • 1
    Because it has Linux client
  • 1
    Command palette (CTRL Shift P)
CONS OF GITKRAKEN
  • 3
    Extremely slow when working with large repositories
  • 3
    No edit/fixup in interactive rebase
  • 3
    Hangs occasionally (not as bad as sourcetree)
  • 2
    Not as many features as sourcetree
  • 2
    Do not allow to directly edit staging area
  • 2
    Does not work like a Mac app

related GitKraken posts

Cees Timmerman

Tower appears to be between GitKraken and SourceTree in detail, but gave two scary error dialogs when attempting to merge resulted in a conflict. Doing the same in SourceTree just worked and showed the conflict in its handy file view that's always visible (unlike Tower's mere "Merge branch 'X' into develop" message when the commit is selected).

Both GitKraken and Tower lack the commit hash in their history overview, requiring one to select a commit to see it.

GitKraken appears to be the only Windows 10 Git GUI suitable for night shifts, but like Tower is only free for 30 days, unlike SourceTree.

See more

GitKraken is the best git client so far. The user interface is very friendly. Everything is easy to do with this tool. A branch tree vizualization is very clear. I've tried SourceTree and I got lost in such many panels. Also performance of SourceTree is not as goot as GitKraken. I like Sublime Merge but it doesn't have so many features as the other tools. I've choosen GitKraken and as bonus I got GitKraken Glo that is the next perfect tool.

See more
Bitbucket logo

Bitbucket

39.9K
32.2K
2.8K
One place to plan projects, collaborate on code, test and deploy, all with free private repositories
39.9K
32.2K
+ 1
2.8K
PROS OF BITBUCKET
  • 904
    Free private repos
  • 397
    Simple setup
  • 348
    Nice ui and tools
  • 341
    Unlimited private repositories
  • 240
    Affordable git hosting
  • 123
    Integrates with many apis and services
  • 119
    Reliable uptime
  • 87
    Nice gui
  • 85
    Pull requests and code reviews
  • 58
    Very customisable
  • 16
    Mercurial repositories
  • 14
    SourceTree integration
  • 12
    JIRA integration
  • 10
    Track every commit to an issue in JIRA
  • 8
    Deployment hooks
  • 8
    Best free alternative to Github
  • 7
    Automatically share repositories with all your teammates
  • 7
    Compatible with Mac and Windows
  • 6
    Source Code Insight
  • 6
    Price
  • 5
    Login with Google
  • 5
    Create a wiki
  • 5
    Approve pull request button
  • 4
    Customizable pipelines
  • 4
    #2 Atlassian Product after JIRA
  • 3
    Also supports Mercurial
  • 3
    Unlimited Private Repos at no cost
  • 3
    Continuous Integration and Delivery
  • 2
    Academic license program
  • 2
    Multilingual interface
  • 2
    Teamcity
  • 2
    Open source friendly
  • 2
    Issues tracker
  • 2
    IAM
  • 2
    IAM integration
  • 2
    Mercurial Support
CONS OF BITBUCKET
  • 19
    Not much community activity
  • 17
    Difficult to review prs because of confusing ui
  • 15
    Quite buggy
  • 10
    Managed by enterprise Java company
  • 8
    CI tool is not free of charge
  • 7
    Complexity with rights management
  • 6
    Only 5 collaborators for private repos
  • 4
    Slow performance
  • 2
    No AWS Codepipelines integration
  • 1
    No more Mercurial repositories
  • 1
    No server side git-hook support

related Bitbucket posts

Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 944.2K views

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Shared insights
on
GitHubGitHubGitLabGitLabBitbucketBitbucket

A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

  • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
  • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
  • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

  • Wiki and project repositories
  • Project uploads
  • The configuration including webhooks and services
  • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

So go ahead with better understanding.

See more
Tower logo

Tower

208
359
80
The most powerful Git client for Mac & Windows
208
359
+ 1
80
PROS OF TOWER
  • 19
    Git
  • 16
    Just works
  • 10
    Version control
  • 6
    Awesome
  • 6
    Simple layout
  • 4
    Multiple windows
  • 3
    Automatic repo discovery
  • 3
    Multiple tabs
  • 2
    Submodule support
  • 2
    Github integration
  • 2
    Full featured client
  • 2
    Uses standard git terminology and methods
  • 2
    Gitflow support
  • 2
    Interactive stage or discard by hunks or lines
  • 1
    SAS
CONS OF TOWER
  • 5
    Expensive
  • 4
    Subscription based
  • 1
    No side by side diff
  • 0
    Merge conflict resolution impossible/unclear

related Tower posts

Cees Timmerman

Tower appears to be between GitKraken and SourceTree in detail, but gave two scary error dialogs when attempting to merge resulted in a conflict. Doing the same in SourceTree just worked and showed the conflict in its handy file view that's always visible (unlike Tower's mere "Merge branch 'X' into develop" message when the commit is selected).

Both GitKraken and Tower lack the commit hash in their history overview, requiring one to select a commit to see it.

GitKraken appears to be the only Windows 10 Git GUI suitable for night shifts, but like Tower is only free for 30 days, unlike SourceTree.

See more
GitHub logo

GitHub

277.1K
240.9K
10.3K
Powerful collaboration, review, and code management for open source and private development projects
277.1K
240.9K
+ 1
10.3K
PROS OF GITHUB
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.3K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 867
    Easy setup
  • 504
    Issue tracker
  • 486
    Great community
  • 482
    Remote team collaboration
  • 451
    Great way to share
  • 442
    Pull request and features planning
  • 147
    Just works
  • 132
    Integrated in many tools
  • 121
    Free Public Repos
  • 116
    Github Gists
  • 112
    Github pages
  • 83
    Easy to find repos
  • 62
    Open source
  • 60
    It's free
  • 60
    Easy to find projects
  • 56
    Network effect
  • 49
    Extensive API
  • 43
    Organizations
  • 42
    Branching
  • 34
    Developer Profiles
  • 32
    Git Powered Wikis
  • 30
    Great for collaboration
  • 24
    It's fun
  • 23
    Clean interface and good integrations
  • 22
    Community SDK involvement
  • 20
    Learn from others source code
  • 16
    Because: Git
  • 14
    It integrates directly with Azure
  • 10
    Newsfeed
  • 10
    Standard in Open Source collab
  • 8
    Fast
  • 8
    It integrates directly with Hipchat
  • 8
    Beautiful user experience
  • 7
    Easy to discover new code libraries
  • 6
    Smooth integration
  • 6
    Cloud SCM
  • 6
    Nice API
  • 6
    Graphs
  • 6
    Integrations
  • 6
    It's awesome
  • 5
    Quick Onboarding
  • 5
    Remarkable uptime
  • 5
    CI Integration
  • 5
    Hands down best online Git service available
  • 5
    Reliable
  • 4
    Free HTML hosting
  • 4
    Version Control
  • 4
    Simple but powerful
  • 4
    Unlimited Public Repos at no cost
  • 4
    Security options
  • 4
    Loved by developers
  • 4
    Uses GIT
  • 4
    Easy to use and collaborate with others
  • 3
    IAM
  • 3
    Nice to use
  • 3
    Ci
  • 3
    Easy deployment via SSH
  • 2
    Good tools support
  • 2
    Leads the copycats
  • 2
    Free private repos
  • 2
    Free HTML hostings
  • 2
    Easy and efficient maintainance of the projects
  • 2
    Beautiful
  • 2
    Never dethroned
  • 2
    IAM integration
  • 2
    Very Easy to Use
  • 2
    Easy to use
  • 2
    All in one development service
  • 2
    Self Hosted
  • 2
    Issues tracker
  • 2
    Easy source control and everything is backed up
  • 1
    Profound
CONS OF GITHUB
  • 53
    Owned by micrcosoft
  • 37
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 8
    Only 3 collaborators for private repos
  • 3
    Limited featureset for issue management
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 2
    Does not have a graph for showing history like git lens
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit
  • 1
    Expensive

related GitHub posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 8.9M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Fork logo

Fork

196
252
126
Fast and Friendly Git Client for Mac
196
252
+ 1
126
PROS OF FORK
  • 19
    One of the easiest and fastest git GUIs
  • 14
    Nice UX
  • 13
    Does the job way better than others
  • 13
    Fast, Great support, Does-it-all, blazing fast
  • 11
    Dark theme
  • 9
    Intuitive interactive rebase and conflict resolution UI
  • 9
    Gitflow support
  • 7
    Excellent commit history tree view
  • 5
    This even looks the same as SourceTree
  • 4
    Repository Manager
  • 3
    Built-in developer feedback
  • 3
    Countless quality of life features
  • 2
    Github Notifications
  • 2
    Not buggy, works smoothly
  • 2
    Keyaboard-only
  • 2
    Visual branch history
  • 2
    Reflog support
  • 1
    Git ammend
  • 1
    Smart 'Open in' menu; e.g. explorer, bit, giithub .
  • 1
    Interactive rebase window
  • 1
    Native application
  • 1
    Intuitive merge conflict resolution
  • 1
    Unique Activity Manager shows current/past operations
CONS OF FORK
  • 2
    Poorly written license
  • 1
    Stability is fragile when looking deeply into history
  • 1
    Merges that require interactive user decision

related Fork posts

Git logo

Git

321.3K
172.2K
6.6K
Fast, scalable, distributed revision control system
321.3K
172.2K
+ 1
6.6K
PROS OF GIT
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 959
    Fast
  • 845
    Open source
  • 726
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Role-based codelines
  • 11
    Disposable Experimentation
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Light
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Easy
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
CONS OF GIT
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 1
    Doesn't scale for big data

related Git posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 8.9M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Ali Soueidan
Creative Web Developer at Ali Soueidan · | 18 upvotes · 1.2M views

Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

Side note: I used npm for package management. 🎉

*Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

See more
Sublime Merge logo

Sublime Merge

115
203
46
A Git client from the makers of Sublime Text
115
203
+ 1
46
PROS OF SUBLIME MERGE
  • 11
    Speed
  • 5
    Hotkeys
  • 5
    Beautify UI
  • 4
    Command Palete
  • 3
    Blame and File History
  • 3
    Submodule Management
  • 3
    Command Line Integration
  • 3
    Commit Editing
  • 3
    Outputs matching git CLI command
  • 3
    Sublime Text Integration
  • 3
    Three-Way Merge
CONS OF SUBLIME MERGE
  • 2
    Only light mode available for evaluation

related Sublime Merge posts

Julian Sanchez
Lead Developer at Chore Champion · | 9 upvotes · 767.1K views

We use Visual Studio Code because it allows us to easily and quickly integrate with Git, much like Sublime Merge ,but it is integrated into the IDE. Another cool part about VS Code is the ability collaborate with each other with Visual Studio Live Share which allows our whole team to get more done together. It brings the convenience of the Google Suite to programming, offering something that works more smoothly than anything found on Atom or Sublime Text

See more

GitKraken is the best git client so far. The user interface is very friendly. Everything is easy to do with this tool. A branch tree vizualization is very clear. I've tried SourceTree and I got lost in such many panels. Also performance of SourceTree is not as goot as GitKraken. I like Sublime Merge but it doesn't have so many features as the other tools. I've choosen GitKraken and as bonus I got GitKraken Glo that is the next perfect tool.

See more
SmartGit logo

SmartGit

38
46
1
A Git Graphical User Interface client
38
46
+ 1
1
PROS OF SMARTGIT
  • 1
    Dark theme
CONS OF SMARTGIT
  • 1
    Non-intuitive actions
  • 1
    Bugs

related SmartGit posts