IMO the only thing that GitHub does better than GitLab is the social networking aspects of the site, which is a major pro. If I were to compare the two platforms only on the basis of tooling for source control, I personally like GitLab quite a bit more. It's nicer to work in. The markdown flavor in GitLab is way better than GitHub's, and it has built in CI/CD and other dev ops things that GitHub doesn't have built in. And, it's not owned by Microsoft.
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I canβt imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesnβt let us chose it for our projects.
For me there are 2 big differences in how they work:
1) Github gives you unlimited public repos while Gitlab gives you unlimited public AND private repos
2) Github gives you most of the QoL features for every repo, no matter if you're paying or not, Gitlab, after the changes they made this year, hides many of those features behind premium plans (like say, squash on merge and things like that)
In my opinion, if you don't want to pay, I'd go with Github for any full Open Source project mainly for the visibility and QoL features and Gitlab if you need to have a more than five-person team and private repos.
The premium options, well that's a whole nother story, you'd have to check some of the features and see what's best for you.
I have to switch between both of them, GitHub is my personal favourite out of the two, I'll use it for work and personal projects. However my university has an agreement with GitLab so we have to use that to submit our course work. I like the aspect of GitLab, but can find some of their interfaces are a little fiddly and takes a bit of time to get use to, especially that they allow private repos and organisation private repos for free straight away (with GitHub you have to pay)
My personal stuff usually open source and goes Github in case it potentially helps someone out there. For the extremely small dev team at my job we rely on Bitbucket when possible because we usually need private repos and super small teams are free.
I use both and also BitBucket. Probably one reason to choose GitLab over GitHub is if you're offended by the Microsoft acquisition of GitHub. I'm not, so it's not a factor for me.
I primarily use GitHub for open-source stuff (here and here). It's free for that and it is the "go-to" place to find open-source projects.
I've been using BitBucket for my own private projects, either just personal or for clients. BitBucket is also free and they do provide the nice SourceTree Git client.
Lately I've started looking at GitLab and have put a few open-source projects on it (here) and I really like it's clean design and overall usability. I like that it is also free for private projects. I may start using this more instead of BitBucket.
As someone that has extensively worked on Bitbucket I'm a bit sad to not see more mentions here π’ Would people mind sharing what their opinion is of Bitbucket? (For context, I was the lead PM for Bitbucket Pipelines a couple years ago)
Javascript Dev, who wants to build amazing things with the MERN stack.
I also have an interest in Data science and Machine-learning.
Getting better every day. Filled with wisdom from above!!
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
A previous company I worked for had all their stuff on Bitbucket (we also used JIRA, tried and quickly abandoned Bamboo, never used Pipelines). My immediate impression of it is that the decision to use Bitbucket is never made without input from someone who routinely wears a suit to work. Like other Atlassian offerings it's enterprise software through and through in that it centers the system rather than the user, with all the consequences you'd expect. There's a lot more effort involved in setting up and managing Bitbucket or especially JIRA than there is in user-centric tools like GitHub or Trello, for example. The effort can be worth it if you're a big enough organization but that's the kind of situation where you know whether you're in it.
Used to use Bitbucket fulltime both professionally and personally. Worked well and had some nice features. As the team got bigger, the price became a real factor and had a hard time selling it to the higher ups.
We tried to work with Pipelines as a replacement for Bamboo which we were completely underusing. We found the YAML wasn't being parsed as expected and the runners felt very flaky. Mixed with the limited minutes for the runners and the almost weekly outages compared to GitLab's very easy runner setup that any team can add a "personal" runner on top of the shared runners if they wanted to, it didn't make sense to keep using the Bitbucket for git repos just for the Jira integration.
Edit: I should note though, we were using the cloud Bitbucket but a self-hosted GitLab core edition. The price comparison isn't 100% fair.
Alyss has been working in tech since 2012, with diverse experience in Sales Engineering, Developer Advocacy, and Product Marketing with companies such as GitHub, Box, Atlassian, and BigCommerce.
When comparing GitHub with GitLab, Bitbucket, or any other Git platform, there's one quintessential difference.
GitHub is a social platform.
With that frame of reference, asking if you should use GitHub or another-Git-platform is like asking if you should use Twitter or a diary. Both allow you to record your thoughts, but the interaction with others is fundamentally changed.
GitHub offers a product that is mindful of open-source needs and workflows. The product itself is well understood by the developer community because of its ubiquitous presence. In terms of users, GitHub claims 24 million developers working across 67 million repos. In 2016, Evans Data (largely regarded as one of the best developer marketing research firms) estimated 21 million developers worldwide. Realistically, that suggests GitHub users may have more than one account and non-developers may have accounts.
GitLab, on the other hand, is not a social platform nor is it just a Git platform. However, as GitLab has evolved, they have mimicked GitHub in their user experience and workflow. For anyone already familiar with GitHub, GitLab was easy to learn. GitLab has focused heavily on the DevOps toolchain in its entirety by offering what they call "Auto DevOps". With GitLab, you can get:
Continuous integration/continuous deployment
More extensive features for issue boards
For smaller teams, individual projects, and OSS, price can be a large (if not the most important factor). GitHub offers free public repos as does GitLab. Bitbucket has free private repos as well as build test minutes.
There's definitely even more I could dive into about why people might choose one or the other, but that gives a high level take on the differences.
Javascript Dev, who wants to build amazing things with the MERN stack.
I also have an interest in Data science and Machine-learning.
Getting better every day. Filled with wisdom from above!!
bitbucket offers free Unlimited private repos for up to 5 users
gitlab offers free unlimited private repos but has no maximal user limit. and 2000 free build minutes.
after the microsoft aquision i would go with gitlab (was going with gitlab already before).
one biiiig plus of gitlab is their transparency. if something goes wrong, they publish nearly every step of their recovery on a public place (status page, twitter and google docs). for me this is much more trustworthy than all the cover up other companies do.
Latest comments (31)
IMO the only thing that GitHub does better than GitLab is the social networking aspects of the site, which is a major pro. If I were to compare the two platforms only on the basis of tooling for source control, I personally like GitLab quite a bit more. It's nicer to work in. The markdown flavor in GitLab is way better than GitHub's, and it has built in CI/CD and other dev ops things that GitHub doesn't have built in. And, it's not owned by Microsoft.
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I canβt imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesnβt let us chose it for our projects.
We have an article here, where we described in details: GitLab vs GitHub in details
For me there are 2 big differences in how they work:
1) Github gives you unlimited public repos while Gitlab gives you unlimited public AND private repos
2) Github gives you most of the QoL features for every repo, no matter if you're paying or not, Gitlab, after the changes they made this year, hides many of those features behind premium plans (like say, squash on merge and things like that)
In my opinion, if you don't want to pay, I'd go with Github for any full Open Source project mainly for the visibility and QoL features and Gitlab if you need to have a more than five-person team and private repos.
The premium options, well that's a whole nother story, you'd have to check some of the features and see what's best for you.
I have to switch between both of them, GitHub is my personal favourite out of the two, I'll use it for work and personal projects. However my university has an agreement with GitLab so we have to use that to submit our course work. I like the aspect of GitLab, but can find some of their interfaces are a little fiddly and takes a bit of time to get use to, especially that they allow private repos and organisation private repos for free straight away (with GitHub you have to pay)
My personal stuff usually open source and goes Github in case it potentially helps someone out there. For the extremely small dev team at my job we rely on Bitbucket when possible because we usually need private repos and super small teams are free.
I use both and also BitBucket. Probably one reason to choose GitLab over GitHub is if you're offended by the Microsoft acquisition of GitHub. I'm not, so it's not a factor for me.
I primarily use GitHub for open-source stuff (here and here). It's free for that and it is the "go-to" place to find open-source projects.
I've been using BitBucket for my own private projects, either just personal or for clients. BitBucket is also free and they do provide the nice SourceTree Git client.
Lately I've started looking at GitLab and have put a few open-source projects on it (here) and I really like it's clean design and overall usability. I like that it is also free for private projects. I may start using this more instead of BitBucket.
I use bitbucket too
I Use gitlab for almost everything, only github if my customers prefer.
Pros on gitlab:
$ git remote add git@gitlab.com:USER/repo.git && git push origin master
creates the repo as privat on gitlab (github dont have that)
Wow that's pretty cool trick ill use that and sadly github doesn't offers that
As someone that has extensively worked on Bitbucket I'm a bit sad to not see more mentions here π’ Would people mind sharing what their opinion is of Bitbucket? (For context, I was the lead PM for Bitbucket Pipelines a couple years ago)
Haven't really used that yet , but I hope I do get the opportuinity to try it out
A previous company I worked for had all their stuff on Bitbucket (we also used JIRA, tried and quickly abandoned Bamboo, never used Pipelines). My immediate impression of it is that the decision to use Bitbucket is never made without input from someone who routinely wears a suit to work. Like other Atlassian offerings it's enterprise software through and through in that it centers the system rather than the user, with all the consequences you'd expect. There's a lot more effort involved in setting up and managing Bitbucket or especially JIRA than there is in user-centric tools like GitHub or Trello, for example. The effort can be worth it if you're a big enough organization but that's the kind of situation where you know whether you're in it.
Used to use Bitbucket fulltime both professionally and personally. Worked well and had some nice features. As the team got bigger, the price became a real factor and had a hard time selling it to the higher ups.
We tried to work with Pipelines as a replacement for Bamboo which we were completely underusing. We found the YAML wasn't being parsed as expected and the runners felt very flaky. Mixed with the limited minutes for the runners and the almost weekly outages compared to GitLab's very easy runner setup that any team can add a "personal" runner on top of the shared runners if they wanted to, it didn't make sense to keep using the Bitbucket for git repos just for the Jira integration.
Edit: I should note though, we were using the cloud Bitbucket but a self-hosted GitLab core edition. The price comparison isn't 100% fair.
When comparing GitHub with GitLab, Bitbucket, or any other Git platform, there's one quintessential difference.
GitHub is a social platform.
With that frame of reference, asking if you should use GitHub or another-Git-platform is like asking if you should use Twitter or a diary. Both allow you to record your thoughts, but the interaction with others is fundamentally changed.
GitHub offers a product that is mindful of open-source needs and workflows. The product itself is well understood by the developer community because of its ubiquitous presence. In terms of users, GitHub claims 24 million developers working across 67 million repos. In 2016, Evans Data (largely regarded as one of the best developer marketing research firms) estimated 21 million developers worldwide. Realistically, that suggests GitHub users may have more than one account and non-developers may have accounts.
GitLab, on the other hand, is not a social platform nor is it just a Git platform. However, as GitLab has evolved, they have mimicked GitHub in their user experience and workflow. For anyone already familiar with GitHub, GitLab was easy to learn. GitLab has focused heavily on the DevOps toolchain in its entirety by offering what they call "Auto DevOps". With GitLab, you can get:
For smaller teams, individual projects, and OSS, price can be a large (if not the most important factor). GitHub offers free public repos as does GitLab. Bitbucket has free private repos as well as build test minutes.
There's definitely even more I could dive into about why people might choose one or the other, but that gives a high level take on the differences.
Well said
@Alyss gitlab has also free private repos.
Unlimited private reposforup to 5 usersafter the microsoft aquision i would go with gitlab (was going with gitlab already before).
one biiiig plus of gitlab is their transparency. if something goes wrong, they publish nearly every step of their recovery on a public place (status page, twitter and google docs). for me this is much more trustworthy than all the cover up other companies do.