Ask YN: What CI do you use instead of GitHub Actions?
When the Zig project moved from GitHub to Codeberg (https://news.ycombinator.com/item?id=46064571), one of the reasons they listed was that "Actions has inexcusable bugs while being completely neglected." (from https://ziglang.org/news/migrating-from-github-to-codeberg/, internal links not copied because I'm being lazy). They did not go into detail about which CI solution they plan to switch to. As I'm starting to get annoyed with GitHub Actions myself and looking for alternatives, I had been hoping to hear their experience with an alternative, but I didn't get that.
So I'd like to ask HN: if you don't use GitHub Actions, what CI solution did you end up choosing? And what has been your experience with it so far? Finally, if you have also used GitHub Actions, how would you compare your current CI solution to GitHub Actions in terms of pros and cons?
P.S. Something with a free tier or a self-hosting option are the only viable options for me, but that doesn't mean I don't want to hear about your experience if you're on a commercial CI solution. Zig team member here: we've migrated to Forgejo Actions [0], which is a system built into Forgejo (the Git forge used by Codeberg) which is very similar to GitHub Actions. In fact, while 1-to-1 compatibility is a non-goal, it's almost compatible---many GHA workflows will run with minimal (or no!) changes, and most Actions written for GHA will work fine (e.g. my setup-zig Action [1] worked without changes). I don't necessarily love the design of GitHub Actions, and obviously that's all inherited in Forgejo Actions, but the issues I have with GitHub's implementation are pretty much all solved in Forgejo (plus they're receptive to PRs if you do need to improve something!). Codeberg offer a couple of free hosted runners (x86_64-linux), though they have quite aggressive usage limits (understandably, since Codeberg can't just throw money at free compute for everyone!) so self-hosting is probably kind of necessary for big-ish projects. That's pretty easy though: the runner [2] is trivial to build (including cross-compiling) and run, and is on the whole just a much more solid piece of software, so it's already been very painless compared to what it was like to self-host GitHub's runner. On the whole, Forgejo Actions has really just felt like a much more refined and cared-for version of GitHub Actions; I'm quite happy with it so far. [0]: https://forgejo.org/docs/latest/user/actions/reference/
[1]: https://codeberg.org/mlugg/setup-zig/
[2]: https://code.forgejo.org/forgejo/runner/ Just FYI, the title of your post should be 'Ask HN: ', not 'Ask YN: '. Oops. Double-checked everything (I thought) before submitting but missed that one. Well, that explains why I didn't see it on the https://news.ycombinator.com/ask page. ... And I don't seem to have the ability to edit the title of my own post? Huh. I would have expected to be able to edit it. HN's UI is deliberately simplistic, which is nice most of the time, but either I'm missing something obvious or there's a bit of functionality missing. Shrug. Well, if there's no way to fix it then I'll wait a while and re-submit with a correct title.