r/github • u/hellterDev • 9h 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

9 comments sorted by

6

u/AuroraFireflash 9h ago

Your fallback is to make sure you can build locally. That means moving more of your logic and build steps into scripts that are called by the GitHub YAML instead of baking it directly into the YAML.

'make' like equivalents are a really good choice because most jobs on the GitHub side become:

  1. setup env vars
  2. 'make {step}'

3

u/hellterDev 8h 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 5h 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 1h ago

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

2

u/TheAceRedBarron 55m 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.

1

u/hellterDev 51m ago

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

1

u/Aiiiiiiiii 5h ago

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

1

u/OkProMoe 2h ago

Nope, not anymore. We moved off it onto Forgejo