Now the best way to use GHA is to do the bare minimum. Put all your CI logic in a script that you can test locally, and just have GHA run your script. Even that is painful. And, somehow, impossible to make secure without having spent 5,000 hours reading all the previous ways people got pwn'd by Github Action's horrendous security model.
My main problem with Gitlab is that after years I still can't find what I'm looking for in the UI. It's always exactly in the third place I look. Otherwise Gitlab has been good. Even self-hosted works pretty well.
* GiLab — Ops centric
* GitHub — Developer centric
if you just want somewhere to stick a code repo and build a release every so often — dont use gitlab, you will not enjoy it.
> My main problem with Gitlab is that after years I still can't find what I'm looking for in the UI.
i still get lost too after several years daily driving gitlab. this is the Ops centric thing. they provide a lot of options. lots of options is good for Ops.
> Now the best way to use GHA is to do the bare minimum
yeah, i’m an ops guy, so the maintaining custom actions stuff on github is horrible for me vs click a button and move on with my day — once i find the button that is! xD
That said, are the majority of people actually even _using_ those features? For us we're essentially just using GitLab for git, merge requests, and CI pipelines. A couple places we use the static page hosting. (First thing I do whenever I create a new repository is go into the settings and just uncheck _all_ the boxes.)
All of that core functionality works really well and is more than polished enough from my point of view.