Follow-Up: GitHub or Gitlab?


GitLab CE is only a small portion of the GitLab featureset even today, and
anything beyond that which isn’t part of CE would have to either be paid
for or reimplemented locally. That’s true regardless whether we consider
the dotcom or self-hosted scenario. And it’s a lot of features, including
some that GitHub makes available to all users (even free accounts). Perhaps
comparisons between the two should focus on those. (“Merge Request Reviews”
was my cherry-pick.)

This isn’t true, the majority of GitLab’s features are implemented in CE, and
the feature matrix is really not useful to see what product is in what
version. Most of the features that are not in CE are useless in practice.
Merge request reviews are in CE.


Are you sure? Because, I just tried it in a personal repository at GNOME’s GitLab, and I saw no sign that’s the case.

By Merge Request Reviews I’m specifically referring to the functionality I linked to in my previous (longer) reply, which was finally released by the antispam gods. GitLab CE lets you comment on code lines, yes, but only individually — not as part of a combined review. That’s a premium feature.

The equivalent functionality in GitHub, however, is accessible to all users. I’ve found it extremely useful when giving feedback on PRs.


We have the ability to put comments in the merge request itself, and in
changes in individual commits. These are present in the merge request view. I
don’t know what more you could be referring to.