| - Github Action's design is much better, just look at [1] for example, there's a lot of low-hanging fruit in Gitlab that's not done for some reason - I've had tons of issues with their kubernetes runners, hard to debug spurious system failures - They still don't display the last N bytes of the logs when logs get long, just the first N bytes, which is entirely useless when a build fails - It's awfully slow to navigate through pipelines, in particular child pipelines - The `stages` things is just useless noise, I just wanna specify dependencies please, I don't want to be forced to also put each job in a stage, it's weird. - You can't expose a secret only to a single job step; they don't really have finer granularity for job steps like Github Actions has -- they just generate a script.sh that's executed directly. - Github has many more reusable actions from the community, I don't think Gitlab has that at all? At least not in a convenient way. [1] https://gitlab.com/gitlab-org/gitlab/-/issues/395964 |
This is the big one.
Github’s ability and dominance in the social space means they have the most active actions ecosystems.
They made actions easier to import share and built marketplaces and now gobs of developers build value into it just for clout (and because they enjoy software of course).
If you think about it carefully, it’s actually a security nightmare. You have no idea what a random Github action you “uses:”d is doing, but in practice 90%+ of the time it doesn’t matter, you get good functionality and save time for free.