4 ms·

I've been comparing Github and Gitlab over the last few weeks. Gitlab had a few more features in the web interface, which is why we chose it for a current proje

I've been comparing Github and Gitlab over the last few weeks. Gitlab had a few more features in the web interface, which is why we chose it for a current project. Github has added these features last week, mostly thanks to pressure, which is good. Here's where Gitlab is lacking though: It's quite buggy, its API is nowhere near as good as Github's and there is no way to secure webhooks, which IMO is quite a big deal. If I'd decide today for another project I'd just pay Github 7$ a month and be done with it. In fact if we keep having issues that's exactly what we'll do - migrating in a git world is quite easy for the points mentioned in the article. I've been quite impressed how Github has acted over the last weeks - when there's actually an outcry they're quite nimble and can react quickly. They've noticed the competition catching up and shot themselves ahead of the curve again.

Gratsby 11y ago
We used Github enterprise at my previous job, GitLab at my current one. The only driver - GitLab is free. GitLab is painful if you have a lot of experience with Github. Feature comparison is pretty similar, but then again a feature comparison with any SVN web interface is pretty similar too. I can't pinpoint it, but I'm much more likely to browse, review, and offer pull requests in a github instance. It's intuitive and I'm used to it.
- m_mueller 11y ago
  I can't say that I'm bothered with Gitlab's interface, even though I've had much more experience with Github. It uses more colors which sometimes has the effect of making actionable clicks stand out better. Commenting on committed code is one such example, for some reason that UI feels more clear to me. Also, on github I sometimes find myself looking for the commit list, which I always find immediately on Gitlab. IMO if you're used to both UIs it's either a wash or slightly in favour of Gitlab - my issues are purely in the backend.
  - rms_returns 11y ago
    How trivial it is to send/accept pull-requests with Gitlab? This is one Github feature which I'm highly dependent on. Unlike Mr. Torvalds, we all aren't experts in sending and managing signed pull-requests by emails. Maybe, I'll learn that one day, but Github's features have made me quite lethargic!
    - sytse 11y ago
      GitLab has merge-requests that work very similar. Accepting them should be easier since we have auto-merge on build success https://about.gitlab.com/2015/12/22/gitlab-8-3-released/ https://about.gitlab.com/2015/12/22/gitlab-8-3-released/
    - deleted 11y ago
      [deleted]
- afarrell 11y ago
  If GitLab is painful to use and that causes you or your employees to spend extra time dealing with that pain, then GitLab may be free as in speech, but it is not free as in beer.
  - beerbajay 11y ago
    It can still be "free as in beer" if there's side-effects; doesn't beer force you to deal with certain kinds of pain, even though it's free?
    - afarrell 11y ago
      Negligible effects since I 2 drinks makes me stop enjoying alcohol. My point is that if you are making a buisiness decision and only thinking of the invoices, you aren't counting your costs well.
hinkley 11y ago
It's $25 a month if you want to manage teams. Wish I'd known that before I switched off bitbucket.
- m_mueller 11y ago
  what does that mean, you can't add collaborators to your 7$ a month project?
  - jsprogrammer 11y ago
    As of the last couple months, you can add collaborators to your project.
    - m_mueller 11y ago
      thanks for the heads up!
  - bojo 11y ago
    You've always been able to add collaborators to private projects. What you miss out on is the team features, which isn't very much if you have a small team.
- atonse 11y ago
  Are your team's salaries so low that $25 a month is a noticeable cost? I can't think of any situation involving multiple paid employees where $25 is anything but a rounding error.
sytse 11y ago
I'm sorry to hear GitLab has not been solid for you. What bugs have you been affected by? What can we improve in our API? Regarding securing webhooks do you mean https://developer.github.com/webhooks/securing/ https://developer.github.com/webhooks/securing/ ?
- m_mueller 11y ago
  I've already opened up some issues[1]. What you point to is what I mean, in addition a reverse IP lookup is also useful to tighten security a bit [2], but it's not mandatory. Specifying a secret is IMO the easiest way to have some peace of mind when it comes to accepting hooks. Regarding the API, I mainly found the documentation more difficult to navigate. There doesn't seem a section specifically for gitlab.com, so I just have to assume that 'community edition' applies there. I haven't found a place where the API endpoint for a gitlab.com profile is described, just took a bit of trial and error - and whatever isn't documented for an API I don't like to rely on. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sort=id_desc&state=opened&utf8=&author_id=381258&assignee_id=&milestone_title=&label_name=&weight= https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sor... [2] https://developer.github.com/v3/meta/ https://developer.github.com/v3/meta/
  - sytse 11y ago
    Thanks for opening those issues days ago! I already marked the documentation issue https://gitlab.com/gitlab-org/gitlab-ce/issues/13479 https://gitlab.com/gitlab-org/gitlab-ce/issues/13479 for the attention of our technical writer 5 days ago. I think having the ability to specify a secret from webhooks makes sense and have asked our CTO and VP of Product for comments in https://gitlab.com/gitlab-org/gitlab-ce/issues/13478 https://gitlab.com/gitlab-org/gitlab-ce/issues/13478. GitLab.com runs GitLab EE, this is displayed at the top of https://about.gitlab.com/gitlab-com/ https://about.gitlab.com/gitlab-com/ but please let me know if there is another logical place. The API endpoint paths are the same for all GitLab servers so https://gitlab.example.com/api https://gitlab.example.com/api becomes https://gitlab.com/api https://gitlab.com/api. I've made an issue to discuss replacing the example.com url with gitlab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/13643 https://gitlab.com/gitlab-org/gitlab-ce/issues/13643 Thanks for all your feedback and creating issues!

Gratsby 11y ago

We used Github enterprise at my previous job, GitLab at my current one. The only driver - GitLab is free. GitLab is painful if you have a lot of experience with Github. Feature comparison is pretty similar, but then again a feature comparison with any SVN web interface is pretty similar too. I can't pinpoint it, but I'm much more likely to browse, review, and offer pull requests in a github instance. It's intuitive and I'm used to it.

m_mueller 11y ago
I can't say that I'm bothered with Gitlab's interface, even though I've had much more experience with Github. It uses more colors which sometimes has the effect of making actionable clicks stand out better. Commenting on committed code is one such example, for some reason that UI feels more clear to me. Also, on github I sometimes find myself looking for the commit list, which I always find immediately on Gitlab. IMO if you're used to both UIs it's either a wash or slightly in favour of Gitlab - my issues are purely in the backend.
- rms_returns 11y ago
  How trivial it is to send/accept pull-requests with Gitlab? This is one Github feature which I'm highly dependent on. Unlike Mr. Torvalds, we all aren't experts in sending and managing signed pull-requests by emails. Maybe, I'll learn that one day, but Github's features have made me quite lethargic!
  - sytse 11y ago
    GitLab has merge-requests that work very similar. Accepting them should be easier since we have auto-merge on build success https://about.gitlab.com/2015/12/22/gitlab-8-3-released/ https://about.gitlab.com/2015/12/22/gitlab-8-3-released/
  - deleted 11y ago
    [deleted]
afarrell 11y ago
If GitLab is painful to use and that causes you or your employees to spend extra time dealing with that pain, then GitLab may be free as in speech, but it is not free as in beer.
- beerbajay 11y ago
  It can still be "free as in beer" if there's side-effects; doesn't beer force you to deal with certain kinds of pain, even though it's free?
  - afarrell 11y ago
    Negligible effects since I 2 drinks makes me stop enjoying alcohol. My point is that if you are making a buisiness decision and only thinking of the invoices, you aren't counting your costs well.

hinkley 11y ago

It's $25 a month if you want to manage teams. Wish I'd known that before I switched off bitbucket.

m_mueller 11y ago
what does that mean, you can't add collaborators to your 7$ a month project?
- jsprogrammer 11y ago
  As of the last couple months, you can add collaborators to your project.
  - m_mueller 11y ago
    thanks for the heads up!
- bojo 11y ago
  You've always been able to add collaborators to private projects. What you miss out on is the team features, which isn't very much if you have a small team.
atonse 11y ago
Are your team's salaries so low that $25 a month is a noticeable cost? I can't think of any situation involving multiple paid employees where $25 is anything but a rounding error.

sytse 11y ago

I'm sorry to hear GitLab has not been solid for you. What bugs have you been affected by? What can we improve in our API? Regarding securing webhooks do you mean https://developer.github.com/webhooks/securing/ https://developer.github.com/webhooks/securing/ ?

m_mueller 11y ago
I've already opened up some issues[1]. What you point to is what I mean, in addition a reverse IP lookup is also useful to tighten security a bit [2], but it's not mandatory. Specifying a secret is IMO the easiest way to have some peace of mind when it comes to accepting hooks. Regarding the API, I mainly found the documentation more difficult to navigate. There doesn't seem a section specifically for gitlab.com, so I just have to assume that 'community edition' applies there. I haven't found a place where the API endpoint for a gitlab.com profile is described, just took a bit of trial and error - and whatever isn't documented for an API I don't like to rely on. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sort=id_desc&state=opened&utf8=&author_id=381258&assignee_id=&milestone_title=&label_name=&weight= https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sor... [2] https://developer.github.com/v3/meta/ https://developer.github.com/v3/meta/
- sytse 11y ago
  Thanks for opening those issues days ago! I already marked the documentation issue https://gitlab.com/gitlab-org/gitlab-ce/issues/13479 https://gitlab.com/gitlab-org/gitlab-ce/issues/13479 for the attention of our technical writer 5 days ago. I think having the ability to specify a secret from webhooks makes sense and have asked our CTO and VP of Product for comments in https://gitlab.com/gitlab-org/gitlab-ce/issues/13478 https://gitlab.com/gitlab-org/gitlab-ce/issues/13478. GitLab.com runs GitLab EE, this is displayed at the top of https://about.gitlab.com/gitlab-com/ https://about.gitlab.com/gitlab-com/ but please let me know if there is another logical place. The API endpoint paths are the same for all GitLab servers so https://gitlab.example.com/api https://gitlab.example.com/api becomes https://gitlab.com/api https://gitlab.com/api. I've made an issue to discuss replacing the example.com url with gitlab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/13643 https://gitlab.com/gitlab-org/gitlab-ce/issues/13643 Thanks for all your feedback and creating issues!