Comment by ivanjermakov
16 hours ago
> fits so much better in "regular" company/organization projects
How so? I used both at work and they're functionally the same.
16 hours ago
> fits so much better in "regular" company/organization projects
How so? I used both at work and they're functionally the same.
Fundamentally, that's just git with a few common features like pull requests, account management and bug tracking.
Choosing one over the other is just a matter of details. How well it integrates with the corporate network, how pretty it looks, the options regarding CI/CD integration, overall popularity and community, etc... Last time I got to choose, I went with Gitea, because performance was good and it met my needs.
I found it much easier to organize repos hierarchically with GitLab. Permissions also seemed easier to setup.
Gitlab is terrible at cross-group permissions if you use dedicated or self-hosted. Because gitlab.com is made to keep top level groups separate (separate tenants). Things like cross-group MR approval, use of the built-in artifact repositories, terraform module registry, gitlab components, and so on...is very messy...so many granular cross-group allows you have to turn on.
Yeah I agree. There are only very minor differences.
Isn't being able to self host it on your company network a big important feature? Like for all the non-public branches and projects you keep internal. Gives you the same UX for everything.
This sounds pretty annoying though: https://docs.gitlab.com/administration/license_usage/
It is important for some companies. https://docs.github.com/en/enterprise-server@3.22/admin/inst...
3 replies →
That is important or critical in some companies. But that's surely not what they meant by fitting their "mental model" better.