Alternatives to Upsource logo

Alternatives to Upsource

GitLab, GitHub, Crucible, SonarQube, and Bitbucket are the most popular alternatives and competitors to Upsource.
51
75
+ 1
58

What is Upsource and what are its top alternatives?

Upsource summarizes recent changes in your repository, showing commit messages, authors, quick diffs, links to detailed diff views and associated code reviews. A commit graph helps visualize the history of commits, branches and merges in your repository.
Upsource is a tool in the Code Collaboration & Version Control category of a tech stack.

Top Alternatives to Upsource

  • GitLab
    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

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

  • Crucible
    Crucible

    It is a Web-based application primarily aimed at enterprise, and certain features that enable peer review of a code base may be considered enterprise social software. ...

  • SonarQube
    SonarQube

    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving. ...

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

  • Fisheye
    Fisheye

    FishEye provides a read-only window into your Subversion, Perforce, CVS, Git, and Mercurial repositories, all in one place. Keep a pulse on everything about your code: Visualize and report on activity, integrate source with JIRA issues, and search for commits, files, revisions, or people. ...

  • Phabricator
    Phabricator

    Phabricator is a collection of open source web applications that help software companies build better software. ...

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

Upsource alternatives & related posts

GitLab logo

GitLab

50.4K
42.5K
2.4K
Open source self-hosted Git management software
50.4K
42.5K
+ 1
2.4K
PROS OF GITLAB
  • 500
    Self hosted
  • 427
    Free
  • 336
    Has community edition
  • 240
    Easy setup
  • 239
    Familiar interface
  • 132
    Includes many features, including ci
  • 109
    Nice UI
  • 82
    Good integration with gitlabci
  • 55
    Simple setup
  • 33
    Has an official mobile app
  • 32
    Free private repository
  • 29
    Continuous Integration
  • 20
    Open source, great ui (like github)
  • 16
    Slack Integration
  • 11
    Full CI flow
  • 10
    Free and unlimited private git repos
  • 8
    User, group, and project access management is simple
  • 7
    All in one (Git, CI, Agile..)
  • 7
    Intuitive UI
  • 7
    Built-in CI
  • 4
    Both public and private Repositories
  • 3
    So easy to use
  • 3
    It's powerful source code management tool
  • 3
    Issue system
  • 3
    Excellent
  • 3
    Integrated Docker Registry
  • 3
    Build/pipeline definition alongside code
  • 3
    Mattermost Chat client
  • 3
    Full DevOps suite with Git
  • 3
    CI
  • 2
    Dockerized
  • 2
    It's fully integrated
  • 2
    Security and Stable
  • 2
    I like the its runners and executors feature
  • 2
    Because is the best remote host for git repositories
  • 2
    Unlimited free repos & collaborators
  • 2
    On-premises
  • 2
    Free private repos
  • 2
    Low maintenance cost due omnibus-deployment
  • 2
    Great for team collaboration
  • 2
    One-click install through DigitalOcean
  • 1
    Wounderful
  • 1
    Opensource
  • 1
    Not Microsoft Owned
  • 1
    Many private repo
  • 1
    Published IP list for whitelisting (gl-infra#434)
  • 1
    Built-in Docker Registry
  • 1
    The dashboard with deployed environments
  • 1
    Groups of groups
  • 1
    Kubernetes Integration
  • 1
    Multilingual interface
  • 1
    Kubernetes integration with GitLab CI
  • 1
    Native CI
  • 1
    HipChat intergration
  • 1
    It includes everything I need, all packaged with docker
  • 1
    Review Apps feature
  • 1
    Powerful software planning and maintaining tools
  • 1
    Powerful Continuous Integration System
  • 1
    Beautiful
  • 0
    Supports Radius/Ldap & Browser Code Edits
CONS OF GITLAB
  • 27
    Slow ui performance
  • 7
    Introduce breaking bugs every release
  • 5
    Insecure (no published IP list for whitelisting)
  • 1
    Built-in Docker Registry
  • 0
    Review Apps feature

related GitLab posts

Tim Abbott
Shared insights
on
GitHubGitHubGitLabGitLab
at

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 402.8K views

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
GitHub logo

GitHub

226K
192.1K
10.2K
Powerful collaboration, review, and code management for open source and private development projects
226K
192.1K
+ 1
10.2K
PROS OF GITHUB
  • 1.8K
    Open source friendly
  • 1.5K
    Easy source control
  • 1.2K
    Nice UI
  • 1.1K
    Great for team collaboration
  • 864
    Easy setup
  • 502
    Issue tracker
  • 484
    Great community
  • 480
    Remote team collaboration
  • 449
    Great way to share
  • 440
    Pull request and features planning
  • 144
    Just works
  • 131
    Integrated in many tools
  • 118
    Free Public Repos
  • 113
    Github Gists
  • 109
    Github pages
  • 82
    Easy to find repos
  • 61
    Open source
  • 59
    It's free
  • 59
    Easy to find projects
  • 56
    Network effect
  • 48
    Extensive API
  • 42
    Organizations
  • 41
    Branching
  • 33
    Developer Profiles
  • 32
    Git Powered Wikis
  • 29
    Great for collaboration
  • 23
    It's fun
  • 22
    Community SDK involvement
  • 22
    Clean interface and good integrations
  • 19
    Learn from others source code
  • 15
    Because: Git
  • 14
    It integrates directly with Azure
  • 9
    Standard in Open Source collab
  • 9
    Newsfeed
  • 8
    It integrates directly with Hipchat
  • 7
    Fast
  • 7
    Beautiful user experience
  • 6
    Cloud SCM
  • 6
    Easy to discover new code libraries
  • 5
    Smooth integration
  • 5
    It's awesome
  • 5
    Integrations
  • 5
    Graphs
  • 5
    Nice API
  • 4
    Quick Onboarding
  • 4
    Remarkable uptime
  • 4
    Hands down best online Git service available
  • 4
    CI Integration
  • 4
    Reliable
  • 3
    Loved by developers
  • 3
    Free HTML hosting
  • 3
    Security options
  • 3
    Simple but powerful
  • 3
    Uses GIT
  • 3
    Unlimited Public Repos at no cost
  • 3
    Version Control
  • 3
    Easy to use and collaborate with others
  • 2
    Nice to use
  • 2
    IAM
  • 2
    Ci
  • 1
    Easy and efficient maintainance of the projects
  • 1
    Good tools support
  • 1
    Beautiful
  • 1
    Free HTML hostings
  • 1
    Self Hosted
  • 1
    All in one development service
  • 1
    Easy to use
  • 1
    Easy source control and everything is backed up
  • 1
    Leads the copycats
  • 1
    Never dethroned
  • 1
    IAM integration
  • 1
    Issues tracker
  • 1
    Very Easy to Use
  • 1
    Easy deployment via SSH
  • 1
    Free private repos
  • 0
    Profound
CONS OF GITHUB
  • 51
    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
    Have to use a token for the package registry
  • 1
    No multilingual interface
  • 1
    Takes a long time to commit

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 · | 29 upvotes · 4.6M 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
Crucible logo

Crucible

54
101
12
Review code, discuss changes, share knowledge, and identify defects
54
101
+ 1
12
PROS OF CRUCIBLE
  • 5
    JIRA Integration
  • 4
    Post-commit preview
  • 2
    Has a linux version
  • 1
    Pre-commit preview
CONS OF CRUCIBLE
    Be the first to leave a con

    related Crucible posts

    Eric Seibert
    DevOps at Children's Hospital of Philadelphia · | 6 upvotes · 219.1K views

    We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?

    I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?

    So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?

    See more
    Shared insights
    on
    JiraJiraFisheyeFisheyeCrucibleCrucible

    I need a tool to review. So when I searched, I saw Crucible and Fisheye. I have e few questions:

    1. Are Crucible and Fisheye start without Jira integration?
    2. Only for document review, which one should be preferred? What do you think about it?
    3. Am I doing import word document and export same word format? Well, when I upload a document to crucible, Is it possible to output in which format I enter? İs there a fixed format?
    See more
    SonarQube logo

    SonarQube

    1.4K
    1.7K
    48
    Continuous Code Quality
    1.4K
    1.7K
    + 1
    48
    PROS OF SONARQUBE
    • 25
      Tracks code complexity and smell trends
    • 15
      IDE Integration
    • 8
      Complete code Review
    CONS OF SONARQUBE
    • 7
      Sales process is long and unfriendly
    • 7
      Paid support is poor, techs arrogant and unhelpful
    • 1
      Does not integrate with Snyk

    related SonarQube posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.6M 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
    Ganesa Vijayakumar
    Full Stack Coder | Technical Lead · | 19 upvotes · 3M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Bitbucket logo

    Bitbucket

    35.4K
    28.2K
    2.8K
    One place to plan projects, collaborate on code, test and deploy, all with free private repositories
    35.4K
    28.2K
    + 1
    2.8K
    PROS OF BITBUCKET
    • 905
      Free private repos
    • 398
      Simple setup
    • 347
      Nice ui and tools
    • 341
      Unlimited private repositories
    • 240
      Affordable git hosting
    • 123
      Integrates with many apis and services
    • 119
      Reliable uptime
    • 86
      Nice gui
    • 84
      Pull requests and code reviews
    • 58
      Very customisable
    • 16
      Mercurial repositories
    • 14
      SourceTree integration
    • 11
      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
    • 5
      Price
    • 5
      Login with Google
    • 5
      Create a wiki
    • 5
      Approve pull request button
    • 4
      Customizable pipelines
    • 4
      #2 Atlassian Product after JIRA
    • 3
      Unlimited Private Repos at no cost
    • 3
      Continuous Integration and Delivery
    • 3
      Also supports Mercurial
    • 2
      Multilingual interface
    • 2
      Mercurial Support
    • 2
      IAM
    • 2
      Issues tracker
    • 2
      Open source friendly
    • 2
      IAM integration
    • 2
      Academic license program
    • 2
      Teamcity
    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 · 699K 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
    Fisheye logo

    Fisheye

    39
    36
    0
    Search, track, and visualize code changes
    39
    36
    + 1
    0
    PROS OF FISHEYE
      Be the first to leave a pro
      CONS OF FISHEYE
        Be the first to leave a con

        related Fisheye posts

        Phabricator logo

        Phabricator

        222
        312
        187
        Open Source, Software Development Platform
        222
        312
        + 1
        187
        PROS OF PHABRICATOR
        • 33
          Open Source
        • 29
          Code Review
        • 25
          Supports Git/Hg/SVN
        • 18
          Bug Tracking
        • 17
          Audit Source Code
        • 11
          Unlimited Repo Support
        • 10
          Software Engineering Platform
        • 10
          Super fast task creation
        • 9
          Flexible Project Management
        • 8
          Project Management
        • 5
          Self hosted
        • 4
          Building Better Software
        • 2
          Best Integration with Gitlab
        • 2
          Complete set for collaborating on software development
        • 1
          Powerful, Complete, Fast, Reliable and Open Source
        • 1
          Straightforward code review process
        • 1
          Workflow
        • 1
          Very effective system, does all PM & code org needed
        CONS OF PHABRICATOR
          Be the first to leave a con

          related Phabricator posts

          SourceTree logo

          SourceTree

          9K
          6.9K
          722
          A free Git GUI client for Windows and macOS
          9K
          6.9K
          + 1
          722
          PROS OF SOURCETREE
          • 205
            Visual history and branch view
          • 162
            Beautiful UI
          • 134
            Easy repository browsing
          • 86
            Gitflow support
          • 74
            Interactive stage or discard by hunks or lines
          • 21
            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
          • 10
            Crashes often
          • 8
            So many bugs
          • 6
            Fetching is slow sometimes
          • 4
            Very unstable
          • 4
            Can't select text in diff (windows)
          • 4
            Extremely slow
          • 4
            No dark theme (Windows)
          • 2
            Freezes quite frequently
          • 2
            Can't scale window from top corners
          • 2
            Requires bitbucket account
          • 2
            UI blinking
          • 2
            Doesn't differentiate submodules from parent repos
          • 2
            Diff makes tab indentation look like spaces
          • 2
            Windows and Mac versions are very different
          • 2
            Windows version worse than mac version
          • 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
          • 1
            Generally hard to like
          • 1
            No reflog support
          • 1
            Installs to AppData folder (windows)
          • 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 · | 29 upvotes · 4.6M 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