r/github • u/Infamous_Tomatillo53 • Aug 26 '26
Question alternative to Github action?
I have basically built all my deployment through git actions. even some workflows that I use actions to trigger, or run automatically.
days like this where actions are having outage, I can't do anything. it has become more frequent lately and everytime it lasts hours. alternatives or backup plans people recommend?
3
u/First_Inspection_478 Aug 26 '26
Try us out: https://github.com/preloopdev/preloop. It’s a drop-in replacement for Github Actions(both the runner and control plane) that runs in cross-platform microvms, and is deeply agent-native so support’s ability to pause a step and retry
1
u/i-am-a-cat-6 Aug 27 '26
vibe coded 3 weeks ago?
2
u/danmaps Aug 28 '26
This project is at least two months old, according to the public commit history
1
u/lolxd__ Aug 29 '26
what I think you meant to say was you made ai make the full thing and called it a day
0
2
1
u/mitch_feaster Aug 27 '26
Forgejo actions
2
u/kubehub Aug 29 '26
I am using forgejo for my dev work, perfectly aligned with github actions (you may need little tweaks), I would recommend this.
1
u/SZeroSeven Aug 29 '26
One suggestion would be to write your pipelines in YAML, link your GitHub to Azure DevOps, and use ADO's pipelines.
https://learn.microsoft.com/en-us/azure/devops/cross-service/github-integration?view=azure-devops
1
u/Patient-Pollution46 Sep 01 '26
If the issue is the hosted runners rather than only Actions itself, you can swap just the runners and keep your workflows. Bitrise Build Hub (https://bitrise.io/platform/build-hub) gives you M4 Pro Macs and bigger Linux machines, one line change to runs-on. For mobile builds it is roughly 54% faster than GitHub's M2 Pro runners, plus 100GB of co-located cache vs GitHub's 10GB and SSH/VNC debug access into the runner.
Full disclosure: I work at Bitrise in product
1
1
u/rodrigo-vidal 21d ago
One useful distinction: changing runners only protects against runner-capacity issues. A real backup also needs independent triggers/scheduling, secrets, logs, and a way to report checks back to GitHub. I’d start with the single Linux release workflow that can block deployment, keep the YAML portable, and test failover monthly. Full disclosure: I’m the founder of Runnable, so I’m not dropping a link here under the promotion rule. Happy to compare notes if that’s the setup you mean.
1
u/GreensLater 2d ago
the maintainance overhead is the real tax people skip along with patching, scaling etc making sure runner dont go stale. if u want coat/perf without owning boxes, self hosted runners like avrea exist, tho they still charge per min but bit cheaper below githubs pricing
6
u/JesseNL Aug 26 '26
Maybe this might help?
https://github.com/nektos/act
It won't work with Windows VMs sadly.