[sophiabits]

While you might not value it, GitLab’s CI story was for a long time way better than GitHub and even a number of dedicated CI/CD providers. If you want to build and deploy microservices from a monorepo independently based on what changed in a PR, for instance, then GitLab supports that out of the box whereas you need to hack something together yourself on Buildkite.

GitHub actions has significantly reduced the gap, and at least for me that was GitLab’s killer feature.

[stefan_]

Meh, there is something to be said for having "anything" over "nothing", but as with many of GitLab features, you inevitably found yourself deep down some years old issue of theirs to find why something is broken or obviously nonsensical. That's before they went batshit insane on development of even more unfinished stuff, while the core ergonomics (Lint CI button anyone?) continue to border on unusable.

Ironically GitHub actions are now the vastly superior experience, despite the lack of bullshit checkbox features. Turns out you don't need so many of them beyond the basic "run something on a worker" flow.

[trystero]

Just give it a little more time and GitHub Actions will have feature creep too.

[aynyc]

Ah, I see. I never bother with CI features. I was playing with all the CI providers when they came out. Never truly got comfortable with them to run my personal projects. At work, we can't use those anyway.

Thanks for pointing that out!