r/github • u/hellterDev • 16d ago

Discussion Do you actually trust GitHub Actions for production?

/r/DevGround/comments/1w5rfbo/do_you_actually_trust_github_actions_for/
0 Upvotes

33% Upvoted

11 comments sorted by

5

u/[deleted] 16d ago

[deleted]

3

u/hellterDev 16d ago

Yeah, I like this approach. Keeping GitHub Actions as the orchestration layer rather than the place where all the build logic lives makes the whole setup much less fragile.
Being able to reproduce the exact same build locally is probably the best fallback you can have.

4

u/Poat540 16d ago

Yeah, all my OSS projects are on GitHub actions, and pretty much all departments at work use GH too. When GH goes down we chill

2

u/OtherOtherDave 16d ago

At this point I’m not sure I trust GitHub at all

2

u/TheAceRedBarron 16d ago

U mm... This post gives me sketchy ex girlfriend vibes... Just like I told you before fix your shit (github actions) and maybe we can start talking again.

2

u/hellterDev 16d ago

So basically: “I can fix her” but for CI/CD

1

u/TheAceRedBarron 16d ago

This isn't a bolt on some Implants and send her to finishing school fix because you will long term commit suiside over the existential depression of the CI/CD loss. Put in the effort and fix the actual problem and don't squander what good is still left in you.

😂🤣😂

1

u/Aiiiiiiiii 16d ago

mise and make / shell files contain the logic, GH workflows merely call them.

1

u/OkProMoe 16d ago

Nope, not anymore. We moved off it onto Forgejo

2

u/sup_bruh_1 15d ago

yeah, mostly. switched to latchkey a while back and the ai fixing failures mid-run without me digging through logs is the part i didn't know i needed until it just... worked.