Alternatives to TortoiseGit logo

Alternatives to TortoiseGit

TortoiseSVN, GitHub, SourceTree, SmartGit, and Git are the most popular alternatives and competitors to TortoiseGit.
48
86
+ 1
5

What is TortoiseGit and what are its top alternatives?

TortoiseGit is a popular Git client for Windows that allows users to interact with Git repositories using a Windows Explorer-style interface. Its key features include easy integration with Windows Explorer, visual diff and merge tools, and support for common Git operations like pushing, pulling, and branching. However, some limitations of TortoiseGit include a more complex user interface compared to other Git clients and occasional performance issues with large repositories.

  1. GitKraken: GitKraken is a cross-platform Git client with a visually appealing interface, built-in code editor, and support for Git actions like merge and rebase. The pros of GitKraken include its intuitive design and robust feature set, while the cons include a paid pro version for advanced features.

  2. GitHub Desktop: GitHub Desktop is an official Git client from GitHub that provides a streamlined user experience for working with Git repositories. Key features include seamless GitHub integration, visual diff tools, and easy collaboration with other GitHub users. The pros of GitHub Desktop include its simple interface and tight integration with GitHub, while the cons include limited support for advanced Git actions.

  3. SourceTree: SourceTree is a free Git client for Windows and Mac that offers a visual interface for managing Git repositories. It features a simple interface, powerful branching and merging capabilities, and support for Git-flow workflows. The pros of SourceTree include its user-friendly interface and advanced Git features, while the cons include occasional performance issues with large repositories.

  4. SmartGit: SmartGit is a Git client for Windows, Mac, and Linux that provides a comprehensive set of tools for managing Git repositories. It offers features like Git-flow support, interactive rebasing, and built-in SSH client. The pros of SmartGit include its powerful feature set and multi-platform support, while the cons include a steeper learning curve compared to other Git clients.

  5. GitExtensions: GitExtensions is an open-source Git client for Windows that offers an easy-to-use interface for working with Git repositories. It includes features like branch visualization, interactive rebase, and support for Git-flow workflows. The pros of GitExtensions include its open-source nature and robust feature set, while the cons include occasional bugs and limited support for macOS.

  6. Tower: Tower is a Git client for Mac and Windows that provides a visually appealing interface for managing Git repositories. It offers features like visual branch management, code search, and integration with popular Git hosting services. The pros of Tower include its elegant design and seamless integration with Git hosting platforms, while the cons include a relatively high price for the full-featured version.

  7. Plastic SCM: Plastic SCM is a version control system that offers Git support along with its own versioning capabilities. It features a visual merge tool, built-in code review, and support for large files and repositories. The pros of Plastic SCM include its advanced versioning capabilities and support for large projects, while the cons include a steeper learning curve and limited community support compared to Git-based clients.

  8. GitUp: GitUp is a minimalist Git client for Mac that provides a simple interface for common Git actions. It offers features like visual history exploration, interactive rebase, and built-in code editor. The pros of GitUp include its clean design and focus on simplicity, while the cons include limited platform support and lack of advanced Git features.

  9. Mercurial: Mercurial is a distributed version control system that offers a similar workflow to Git but with a focus on ease of use and performance. It features built-in support for large files, powerful branching and merging capabilities, and easy collaboration with other developers. The pros of Mercurial include its simplicity and solid performance, while the cons include a smaller user base compared to Git and limited third-party tool integration.

  10. Magit: Magit is an Emacs interface for Git that provides a powerful set of tools for managing Git repositories directly within the Emacs editor. It offers features like interactive staging, visual diff tools, and seamless integration with Emacs workflows. The pros of Magit include its deep integration with Emacs and customizable workflows, while the cons include a steep learning curve for non-Emacs users.

Top Alternatives to TortoiseGit

  • TortoiseSVN
    TortoiseSVN

    It is an Apache™ Subversion (SVN)® client, implemented as a Windows shell extension. It's intuitive and easy to use, since it doesn't require the Subversion command line client to run. And it is free to use, even in a commercial environment. ...

  • 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. ...

  • SourceTree
    SourceTree

    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. ...

  • 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. ...

  • 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. ...

  • TortoiseHg
    TortoiseHg

    It is a Windows shell extension and a series of applications for the Mercurial distributed revision control system. It also includes a Gnome/Nautilus extension and a CLI wrapper application so the TortoiseHg tools can be used on non-Windows platforms. ...

  • GitKraken
    GitKraken

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

  • 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. ...

TortoiseGit alternatives & related posts

TortoiseSVN logo

TortoiseSVN

46
108
1
A Subversion client, implemented as a Microsoft Windows shell extension
46
108
+ 1
1
PROS OF TORTOISESVN
  • 1
    Easy to use
CONS OF TORTOISESVN
    Be the first to leave a con

    related TortoiseSVN posts

    GitHub logo

    GitHub

    279.5K
    243.8K
    10.3K
    Powerful collaboration, review, and code management for open source and private development projects
    279.5K
    243.8K
    + 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
    Russel Werner
    Lead Engineer at StackShare · | 32 upvotes · 2.2M views

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more
    SourceTree logo

    SourceTree

    10.4K
    7.9K
    727
    A free Git GUI client for Windows and macOS
    10.4K
    7.9K
    + 1
    727
    PROS OF SOURCETREE
    • 205
      Visual history and branch view
    • 164
      Beautiful UI
    • 134
      Easy repository browsing
    • 87
      Gitflow support
    • 75
      Interactive stage or discard by hunks or lines
    • 22
      Great branch visualization
    • 18
      Ui/ux and user-friendliness
    • 8
      Best Git Client UI/Features
    • 7
      Search commit messages
    • 5
      Available for Windows and macOS
    • 1
      Log only one file
    • 1
      Search file content
    CONS OF SOURCETREE
    • 12
      Crashes often
    • 8
      So many bugs
    • 7
      Fetching is slow sometimes
    • 5
      No dark theme (Windows)
    • 5
      Extremely slow
    • 5
      Very unstable
    • 4
      Can't select text in diff (windows)
    • 3
      Freezes quite frequently
    • 3
      Can't scale window from top corners
    • 2
      UI blinking
    • 2
      Windows version worse than mac version
    • 2
      Installs to AppData folder (windows)
    • 2
      Diff makes tab indentation look like spaces
    • 2
      Windows and Mac versions are very different
    • 2
      Diff appears as if space indented even if its tabs
    • 2
      Doesn't have an option for git init
    • 2
      Useless for merge conflict resolution
    • 2
      Doesn't differentiate submodules from parent repos
    • 2
      Requires bitbucket account
    • 1
      Generally hard to like
    • 1
      No reflog support
    • 1
      Bases binary check on filesize
    • 1
      Can't add remotes by right clicking remotes (windows)

    related SourceTree posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.2M 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
    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
    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

    Git logo

    Git

    289.8K
    174.2K
    6.6K
    Fast, scalable, distributed revision control system
    289.8K
    174.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 · 9.2M 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
    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 23 upvotes · 8.3M views

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more
    TortoiseHg logo

    TortoiseHg

    8
    12
    0
    A set of graphical tools and a shell extension for the Mercurial distributed revision control system
    8
    12
    + 1
    0
    PROS OF TORTOISEHG
      Be the first to leave a pro
      CONS OF TORTOISEHG
        Be the first to leave a con

        related TortoiseHg posts

        GitKraken logo

        GitKraken

        719
        908
        279
        Git GUI Client for Windows Mac and Linux built on Electron
        719
        908
        + 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
        Fork logo

        Fork

        198
        254
        126
        Fast and Friendly Git Client for Mac
        198
        254
        + 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