What do you mean by losing free CI running? Codeberg has two free-of-charge CI offerings: Forgejo Actions and Woodpecker CI.
Forgejo Actions is enabled by default for all accounts. Woodpecker does require an explicit access to be granted, but it's fast and easy to request. You just create an issue here: https://codeberg.org/Codeberg-e.V./requests
Big projects like Zig have managed to migrate to Codeberg: https://codeberg.org/ziglang
Don't get me wrong I'm not a codeberg hater, but there are realistic caveats to consider. Last I remember (maybe they changed some of this):
You have to request access to CI from codeberg last I checked. They then confirm that it's an approved FLOSS project. With GitHub you just get the access right away.
CI use on codeberg is being done through donated hardware by users so while they don't have quota limits they are not in a situation where you can "reliably" (in principle, in practice GitHub uptime is a meme) just spin up more CI indefinitely the way Microsoft Azure-backed GitHub can. Github allows you to have unlimited CI minutes as long as it's a public repo, codeberg does not.
Codeberg only has Linux runners currently, no MacOS or Windows runners, if you wanted more thorough regression testing automated.
You have to request access to CI from codeberg last I checked. They then confirm that it's an approved FLOSS project. With GitHub you just get the access right away.
Yes, this is still true. But I recently went through this and got approved within a few hours. This isn't really a big deal.
However, yeah, I can see how points 2 and 3 may be more relevant. Both could be solved by self-hosting some runners if there were interest.
Thread
Comment by @birdybro
Comment by @tgf9
Comment by @birdybro
Comment by @tgf9