Alternatives to TortoiseSVN logo

Alternatives to TortoiseSVN

TortoiseGit, SVN (Subversion), Git, TortoiseHg, and GitHub are the most popular alternatives and competitors to TortoiseSVN.
38
85
+ 1
0

What is TortoiseSVN and what are its top alternatives?

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.
TortoiseSVN is a tool in the Visual Version Control category of a tech stack.

Top Alternatives to TortoiseSVN

  • TortoiseGit
    TortoiseGit

    It is a Git revision control client, implemented as a Windows shell extension and based on TortoiseSVN. It is free software released under the GNU General Public License. ...

  • SVN (Subversion)
    SVN (Subversion)

    Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ...

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

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

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

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

  • GitHub Enterprise
    GitHub Enterprise

    GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services. ...

TortoiseSVN alternatives & related posts

TortoiseGit logo

TortoiseGit

45
69
4
The Power of Git in a Windows Shell
45
69
+ 1
4
PROS OF TORTOISEGIT
  • 4
    Turns Explorer into a git client
CONS OF TORTOISEGIT
    Be the first to leave a con

    related TortoiseGit posts

    SVN (Subversion) logo

    SVN (Subversion)

    765
    588
    43
    Enterprise-class centralized version control for the masses
    765
    588
    + 1
    43
    PROS OF SVN (SUBVERSION)
    • 20
      Easy to use
    • 13
      Simple code versioning
    • 5
      User/Access Management
    • 3
      Complicated code versionioning by Subversion
    • 2
      Free
    CONS OF SVN (SUBVERSION)
    • 7
      Branching and tagging use tons of disk space

    related SVN (Subversion) posts

    I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

    • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

    • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

    • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

    • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

    • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

    • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

    • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

    See more
    rishig
    Head of Product at Zulip · | 8 upvotes · 125.6K views
    Shared insights
    on
    GitGitSVN (Subversion)SVN (Subversion)
    at

    I use Git instead of SVN (Subversion) because it allows us to scale our development team. At any given time, the Zulip open source project has hundreds of open pull requests from tens of contributors, each in various stages of the pipeline. Git's workflow makes it very easy to context switch between different feature branches.

    See more
    Git logo

    Git

    172K
    146.7K
    6.6K
    Fast, scalable, distributed revision control system
    172K
    146.7K
    + 1
    6.6K
    PROS OF GIT
    • 1.4K
      Distributed version control system
    • 1.1K
      Efficient branching and merging
    • 960
      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

    related Git posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M 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 · 951.6K 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
    TortoiseHg logo

    TortoiseHg

    8
    11
    0
    A set of graphical tools and a shell extension for the Mercurial distributed revision control system
    8
    11
    + 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

        GitHub logo

        GitHub

        237.9K
        203.6K
        10.2K
        Powerful collaboration, review, and code management for open source and private development projects
        237.9K
        203.6K
        + 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
        • 114
          Github Gists
        • 109
          Github pages
        • 82
          Easy to find repos
        • 61
          Open source
        • 59
          Easy to find projects
        • 59
          It's free
        • 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 · 5M 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
        GitLab logo

        GitLab

        52.9K
        44.7K
        2.4K
        Open source self-hosted Git management software
        52.9K
        44.7K
        + 1
        2.4K
        PROS OF GITLAB
        • 501
          Self hosted
        • 428
          Free
        • 336
          Has community edition
        • 241
          Easy setup
        • 239
          Familiar interface
        • 133
          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
        • 12
          Full CI flow
        • 10
          Free and unlimited private git repos
        • 8
          User, group, and project access management is simple
        • 7
          Intuitive UI
        • 7
          Built-in CI
        • 7
          All in one (Git, CI, Agile..)
        • 4
          Both public and private Repositories
        • 3
          Integrated Docker Registry
        • 3
          CI
        • 3
          Full DevOps suite with Git
        • 3
          It's powerful source code management tool
        • 3
          Excellent
        • 3
          Build/pipeline definition alongside code
        • 3
          Mattermost Chat client
        • 3
          Issue system
        • 3
          So easy to use
        • 2
          Because is the best remote host for git repositories
        • 2
          Dockerized
        • 2
          Free private repos
        • 2
          Great for team collaboration
        • 2
          Unlimited free repos & collaborators
        • 2
          It's fully integrated
        • 2
          I like the its runners and executors feature
        • 2
          One-click install through DigitalOcean
        • 2
          Security and Stable
        • 2
          Low maintenance cost due omnibus-deployment
        • 2
          On-premises
        • 1
          Kubernetes integration with GitLab CI
        • 1
          Multilingual interface
        • 1
          Review Apps feature
        • 1
          Powerful software planning and maintaining tools
        • 1
          Groups of groups
        • 1
          Built-in Docker Registry
        • 1
          Beautiful
        • 1
          Wounderful
        • 1
          Opensource
        • 1
          Not Microsoft Owned
        • 1
          Many private repo
        • 1
          Published IP list for whitelisting (gl-infra#434)
        • 1
          The dashboard with deployed environments
        • 1
          Powerful Continuous Integration System
        • 1
          Kubernetes Integration
        • 1
          Native CI
        • 1
          HipChat intergration
        • 1
          It includes everything I need, all packaged with docker
        • 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 · 443.5K 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
        Bitbucket logo

        Bitbucket

        36.6K
        29.3K
        2.8K
        One place to plan projects, collaborate on code, test and deploy, all with free private repositories
        36.6K
        29.3K
        + 1
        2.8K
        PROS OF BITBUCKET
        • 904
          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 · 721.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
        GitHub Enterprise logo

        GitHub Enterprise

        507
        606
        9
        The on-premises version of GitHub, which you can deploy and manage in your own, secure environment
        507
        606
        + 1
        9
        PROS OF GITHUB ENTERPRISE
        • 3
          Expensive - $$$
        • 2
          Code security
        • 2
          CDCI with Github Actions
        • 1
          Both Cloud and Enterprise Server Versions available
        • 1
          Draft Pull Request
        • 0
          User experience
        CONS OF GITHUB ENTERPRISE
        • 2
          $$$

        related GitHub Enterprise posts

        Matanel Crown
        Software Developer at BBT.live · | 7 upvotes · 150.4K views

        Hi all,

        I would like some information regarding the benefits an aspiring start-up company may have, while using GitHub Enterprise vs the regular GitHub package. On a separate issue, I'd like to understand whether GitLab may have some DevOps-related advantages GitHub does not.

        Thank you in advance, Matt

        See more
        Eric Seibert
        DevOps at Children's Hospital of Philadelphia · | 6 upvotes · 258.6K 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