It's funny how we traded server maintenance for CI vendor lock-in and now keep circling back to which pain we hate more.
I use Namespace (https://namespace.so) and I hook it up both to my personal GitHub as well as my personal Forgejo. I’m in the process of moving from the former to the latter!
Granted, self-hosting git is not feasible for everyone, but GitHub + self hosted runners seems like a very good option.
I assume this isn't optimal for a business setup, but for personal projects, I don't miss GitHub Actions at all.
It seems like to be a serious CI platform they really need to change Windows and Mac binaries for runners so you can build for those platforms.
And this is more of a Forgejo issue than a Codeberg issue specifically.
But also, I’d also throw out there the idea that CI doesn’t have to be at the same website as your source control. It’s nice that GitHub actions are conveniently part of the product but it’s not even really the top CI system out there.
A contributor maintains a tested re-release of Forgejo Runner for Windows: https://github.com/Crown0815/Forgejo-runner-windows-builder
But, pull it down and build it, and it will work.