Forgejo Actions is what Zig has migrated to. It's very similar to GitHub Actions; the downside of that is that you inherit questionable design choices, but the big upside is that migration is super easy. While they don't target 1:1 compatibility, things are similar enough that you basically only need to tweak workflow files very slightly. Our experience so far is that it fixes most of our serious problems with GitHub Actions; in particular, their runner software is significantly easier to deploy and configure, has much better target support (GitHub's runner is essentially impossible to use outside of x86_64/aarch64 linux/windows/macos; we tried to patch it to support riscv64-linux and got stuck on some nonsensical problems on GitHub's side!), and actually accepts contributions & responds to issues. My issues with the GitHub Actions' backend & web interface (of which I have many) are pretty much all gone, too, with no new issues taking their place.

I don't like Azure DevOps or it's pipelines (the yaml ones, not the classic drag and drop that is now disabled by default), but I like it a lot more than github actions. I doubt we'd ever really use github actions for security reasons, but I do prefer the explicit behaviors and templating with structure with azure compared to how Github Actions tries to solve change management with digitalisation. I can totally see why github actions would make more sense if you don't have enterprise organisation type AD/Entra + Azure though.

Gitlab CI is leagues better