Alternatives to Bit logo

Alternatives to Bit

Cobalt, Bitly, Storybook, npm, and Lerna are the most popular alternatives and competitors to Bit.
29
106
+ 1
0

What is Bit and what are its top alternatives?

It is open source tool that helps you easily publish and manage reusable components. It help teams scale shared components to hundreds and even thousands of components, while eliminating the overhead around this process.
Bit is a tool in the Code Collaboration & Version Control category of a tech stack.
Bit is an open source tool with 14.6K GitHub stars and 798 GitHub forks. Here’s a link to Bit's open source repository on GitHub

Top Alternatives to Bit

  • Cobalt

    Cobalt

    Sign up for free in just a few minutes and ask our top researchers to evaluate the security of your web or mobile app. Decide to run either a bug bounty program or an agile crowdsourced security audit. Choose from our Core of vetted researchers or the whole Crowd. ...

  • Bitly

    Bitly

    Get the most out of your social and online marketing efforts. Own, understand and activate your best audience through the power of the link with Bitly Brand Tools. ...

  • Storybook

    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

  • npm

    npm

    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day. ...

  • Lerna

    Lerna

    It is a popular and widely used package written in JavaScript. It optimizes the workflow around managing multi-package repositories with git and npm. ...

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

Bit alternatives & related posts

Cobalt logo

Cobalt

5
26
0
Public bug bounty programs
5
26
+ 1
0
PROS OF COBALT
    Be the first to leave a pro
    CONS OF COBALT
      Be the first to leave a con

      related Cobalt posts

      Bitly logo

      Bitly

      35
      32
      0
      The world's leading link management platform, powering billions of clicks each month across both web and mobile.
      35
      32
      + 1
      0
      PROS OF BITLY
        Be the first to leave a pro
        CONS OF BITLY
          Be the first to leave a con

          related Bitly posts

          Storybook logo

          Storybook

          628
          387
          0
          Build bulletproof UI components faster
          628
          387
          + 1
          0
          PROS OF STORYBOOK
            Be the first to leave a pro
            CONS OF STORYBOOK
              Be the first to leave a con

              related Storybook posts

              Robert Zuber

              We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

              See more
              npm logo

              npm

              71.2K
              55.9K
              1.6K
              The package manager for JavaScript.
              71.2K
              55.9K
              + 1
              1.6K
              PROS OF NPM
              • 649
                Best package management system for javascript
              • 383
                Open-source
              • 327
                Great community
              • 148
                More packages than rubygems, pypi, or packagist
              • 112
                Nice people matter
              • 6
                Audit feature
              • 5
                As fast as yarn but really free of facebook
              • 4
                Good following
              • 1
                Super fast
              • 1
                Stability
              CONS OF NPM
              • 5
                Problems with lockfiles
              • 5
                Bad at package versioning and being deterministic
              • 3
                Node-gyp takes forever
              • 1
                Super slow

              related npm posts

              Simon Reymann
              Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.2M views

              Our whole Node.js backend stack consists of the following tools:

              • Lerna as a tool for multi package and multi repository management
              • npm as package manager
              • NestJS as Node.js framework
              • TypeScript as programming language
              • ExpressJS as web server
              • Swagger UI for visualizing and interacting with the API’s resources
              • Postman as a tool for API development
              • TypeORM as object relational mapping layer
              • JSON Web Token for access token management

              The main reason we have chosen Node.js over PHP is related to the following artifacts:

              • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
              • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
              • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
              • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
              See more
              Johnny Bell

              So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

              So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

              The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

              I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

              Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

              I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

              See more
              Lerna logo

              Lerna

              299
              104
              0
              A tool for managing JavaScript projects
              299
              104
              + 1
              0
              PROS OF LERNA
                Be the first to leave a pro
                CONS OF LERNA
                  Be the first to leave a con

                  related Lerna posts

                  Simon Reymann
                  Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.2M views

                  Our whole Node.js backend stack consists of the following tools:

                  • Lerna as a tool for multi package and multi repository management
                  • npm as package manager
                  • NestJS as Node.js framework
                  • TypeScript as programming language
                  • ExpressJS as web server
                  • Swagger UI for visualizing and interacting with the API’s resources
                  • Postman as a tool for API development
                  • TypeORM as object relational mapping layer
                  • JSON Web Token for access token management

                  The main reason we have chosen Node.js over PHP is related to the following artifacts:

                  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
                  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
                  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
                  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
                  See more
                  GitHub logo

                  GitHub

                  194.2K
                  160.9K
                  10.2K
                  Powerful collaboration, review, and code management for open source and private development projects
                  194.2K
                  160.9K
                  + 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
                  • 861
                    Easy setup
                  • 502
                    Issue tracker
                  • 484
                    Great community
                  • 480
                    Remote team collaboration
                  • 448
                    Great way to share
                  • 441
                    Pull request and features planning
                  • 144
                    Just works
                  • 130
                    Integrated in many tools
                  • 117
                    Free Public Repos
                  • 112
                    Github Gists
                  • 108
                    Github pages
                  • 81
                    Easy to find repos
                  • 60
                    Open source
                  • 58
                    Easy to find projects
                  • 56
                    Network effect
                  • 56
                    It's free
                  • 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
                  • 21
                    Clean interface and good integrations
                  • 19
                    Learn from others source code
                  • 14
                    It integrates directly with Azure
                  • 14
                    Because: Git
                  • 13
                    Wide acceptance
                  • 10
                    Large community
                  • 9
                    Newsfeed
                  • 9
                    Standard in Open Source collab
                  • 8
                    It integrates directly with Hipchat
                  • 7
                    Beautiful user experience
                  • 7
                    Fast
                  • 6
                    Easy to discover new code libraries
                  • 6
                    Cloud SCM
                  • 5
                    Graphs
                  • 5
                    Smooth integration
                  • 5
                    Nice API
                  • 5
                    Integrations
                  • 5
                    It's awesome
                  • 4
                    Remarkable uptime
                  • 4
                    Hands down best online Git service available
                  • 4
                    Reliable
                  • 3
                    Easy to use and collaborate with others
                  • 3
                    CI Integration
                  • 3
                    Free HTML hosting
                  • 3
                    Loved by developers
                  • 3
                    Quick Onboarding
                  • 3
                    Security options
                  • 3
                    Simple but powerful
                  • 3
                    Uses GIT
                  • 3
                    Unlimited Public Repos at no cost
                  • 3
                    Version Control
                  • 2
                    Nice to use
                  • 1
                    Free private repos
                  • 1
                    Easy deployment via SSH
                  • 1
                    Beautiful
                  • 1
                    Owned by micrcosoft
                  • 1
                    Free HTML hostings
                  • 1
                    Self Hosted
                  • 1
                    All in one development service
                  • 1
                    Easy to use
                  • 1
                    Good tools support
                  • 1
                    Easy source control and everything is backed up
                  • 1
                    Leads the copycats
                  • 1
                    Never dethroned
                  • 1
                    Ci
                  • 1
                    Issues tracker
                  • 1
                    Easy and efficient maintainance of the projects
                  • 1
                    IAM
                  • 1
                    IAM integration
                  • 0
                    Profound
                  • 0
                    1
                  CONS OF GITHUB
                  • 48
                    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
                  • 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 · | 28 upvotes · 3.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

                  43.7K
                  36.1K
                  2.3K
                  Open source self-hosted Git management software
                  43.7K
                  36.1K
                  + 1
                  2.3K
                  PROS OF GITLAB
                  • 491
                    Self hosted
                  • 420
                    Free
                  • 334
                    Has community edition
                  • 238
                    Easy setup
                  • 238
                    Familiar interface
                  • 131
                    Includes many features, including ci
                  • 107
                    Nice UI
                  • 81
                    Good integration with gitlabci
                  • 53
                    Simple setup
                  • 33
                    Has an official mobile app
                  • 31
                    Free private repository
                  • 26
                    Continuous Integration
                  • 19
                    Open source, great ui (like github)
                  • 15
                    Slack Integration
                  • 11
                    Full CI flow
                  • 9
                    Free and unlimited private git repos
                  • 8
                    User, group, and project access management is simple
                  • 7
                    Built-in CI
                  • 7
                    All in one (Git, CI, Agile..)
                  • 7
                    Intuitive UI
                  • 4
                    Both public and private Repositories
                  • 3
                    Mattermost Chat client
                  • 3
                    Integrated Docker Registry
                  • 3
                    Issue system
                  • 2
                    One-click install through DigitalOcean
                  • 2
                    Because is the best remote host for git repositories
                  • 2
                    Full DevOps suite with Git
                  • 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
                    CI
                  • 2
                    So easy to use
                  • 2
                    Dockerized
                  • 2
                    It's powerful source code management tool
                  • 2
                    Excellent
                  • 2
                    Build/pipeline definition alongside code
                  • 2
                    Security and Stable
                  • 2
                    Low maintenance cost due omnibus-deployment
                  • 2
                    On-premises
                  • 1
                    Multilingual interface
                  • 1
                    Kubernetes integration with GitLab CI
                  • 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
                    Native CI
                  • 1
                    HipChat intergration
                  • 1
                    Kubernetes Integration
                  • 1
                    The dashboard with deployed environments
                  • 1
                    Powerful Continuous Integration System
                  • 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) · | 18 upvotes · 306.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
                  Bitbucket logo

                  Bitbucket

                  32.3K
                  25.4K
                  2.8K
                  One place to plan projects, collaborate on code, test and deploy, all with free private repositories
                  32.3K
                  25.4K
                  + 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
                    Best free alternative to Github
                  • 8
                    Deployment hooks
                  • 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
                    Continuous Integration and Delivery
                  • 3
                    Unlimited Private Repos at no cost
                  • 3
                    Also supports Mercurial
                  • 2
                    Teamcity
                  • 2
                    Mercurial Support
                  • 2
                    IAM
                  • 2
                    Issues tracker
                  • 2
                    Open source friendly
                  • 2
                    Multilingual interface
                  • 2
                    Academic license program
                  • 2
                    IAM integration
                  • 0
                    Free Private Repositories
                  CONS OF BITBUCKET
                  • 19
                    Not much community activity
                  • 17
                    Difficult to review prs because of confusing ui
                  • 14
                    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 · 639.4K 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