Comment by sytse | Hacker News Reader

Comment by sytse | Hacker News Reader

Parent Full thread

To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship

I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found on about.gitlab.com/features/#compare "

Regarding the examples please help me understand:

1. Can you rebase in the GitHub interface?

2. Does GitHub have an option to fast forward merges?

3. Please let me know if this is a feature people want open sourced. EDIT turns out that this is part of the open source edition already https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/cont... I created https://gitlab.com/gitlab-org/gitlab-ce/issues/22185 to update the docs

4. We have a commit status API in GitLab CE https://docs.gitlab.com/ce/api/commits.html#commit-status and works with the open source https://github.com/jenkinsci/gitlab-plugin We do have additional integration in EE https://docs.gitlab.com/ee/integration/jenkins.html

BTW you might be happy to learn that what you mention as an example of typical "enterprise-y" feature is available in GitLab CE https://docs.gitlab.com/ce/integration/saml.html

So, when reading the features page, I was considering 1 and 2 in terms of a feature that I use at GitHub religiously: squashed pull requests (that are automatically fast-forwarded) [1].

If I'm reading this correctly, this exists in GitLab as an enterprise feature, so I think my earlier comment isn't too far off. There also appears to be some community feedback suggesting this should be a CE feature [2].

[1] https://help.github.com/articles/about-pull-request-merges/ [2] https://gitlab.com/gitlab-org/gitlab-ce/issues/4106

> 1. Can you rebase in the GitHub interface?

> 2. Does GitHub have an option to fast forward merges?

So is Gitlab's aim to just play catchup to Github?

We already have these features, we just opted to make them EE/.com only since we think they are more relevant for organizations that have more than 100 potential users.

We have a broader scope than GitHub, see our announcement broadcasted on Tuesday for more information and a demo https://about.gitlab.com/2016/09/14/gitlab-live-event-recap/

are you joking? it's the other way around. github is only just now playing catch up to gitlab

GitLab has had a larger feature set than GitHub for a long time now.

Github compromises by having a nice ecosystem of tools which you can plug in, but having it built in is always nice since the integration is tighter.

Reply on news.ycombinator.com