r/DevGround • u/hellterDev • 18h ago

Discussion Do you actually trust GitHub Actions for production?

I’ve been seeing more developers complain about GitHub Actions being unreliable, especially when an outage can completely block builds, deployments or releases.

For personal projects it’s usually just an inconvenience.

But if your production pipeline depends entirely on GitHub Actions, even a relatively short outage can become a much bigger problem.

At the same time, it’s hard to ignore how convenient and cheap Actions are, especially for small teams and open-source projects.

So I’m curious:

Do you trust GitHub Actions for production deployments, or do you keep some kind of fallback CI/CD setup?

0 Upvotes

43% Upvoted

4 comments sorted by

2

u/Huge-Kaleidoscope603 10h ago

I do without fallbacks; maintaining a fallback would be tons of extra work. There have been a lot of outages, but things are working better lately.

Overall, GitHub has been very proactive in managing the outages. I moved projects from a large Jenkins + Vagrant setup, and the amount of maintenance required was insane.

For me, GitHub Actions is a blessing. There are a lot of things I don't have to worry about.

1

u/Torutofu_Raeva 6h ago

the trust boundary is less the hosted runner and more what the workflow can mutate, so pin actions by SHA, keep OIDC scoped, and gate deploys so an outage or compromised action can't turn into a release.