6 ms·
I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from
by JLO64 21d ago
I'm in the middle of a Forgejo migration myself for similar reasons. What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix for a bug to my webapp. (I relied on GH Actions to build and push an ARM Docker image.) For work that a business depends on, I can't recommend GitHub Actions. It's not just the outages that personally annoyed me, but the fact that I'm paying for it as well. So far I'm loving Forgejo and have no regrets!
- stephenway 21d agoI'm curious what you're replacing Actions with on the Forgejo side, and whether running that infra yourself feels like part of the benefit or another thing you'd rather not own
- ikidd 21d agoForgejo has Runners that you can install on another server and register with Forgejo Actions. There might be 3rd party Runners you can pay to use, I've just run my own on a hardened VM.
- schmookeeg 21d agoMy gh actions were straightforward and moved to forgejo runners with zero drama.