News for hackers. Stuff that matters.
Re:Any program can be a GitHub Actions shell by misnome on Tuesday April 08, 2025 @05:21AM (#43619757)
Which of any the alternatives don’t have their own unique solution?
Re:Any program can be a GitHub Actions shell by Hackbraten on Tuesday April 08, 2025 @08:18AM (#43620829)
The question was "GitHub CI YAML vs. pipeline.sh", not "GitHub CI YAML vs. other forge’s YAML."

What I’m trying to say is that if you keep your build logic in `pipeline.sh` (and use GitHub CI only for calling into it), then you’re going to have an easier time migrating to another forge’s CI than in the alternative scenario, i.e. if your build logic is coded in GitHub CI YAML.

Re:Any program can be a GitHub Actions shell by misnome on Tuesday April 08, 2025 @02:08PM (#43624761)
Obviously. But then you still have caching, passing data/artifacts between stages, workflow logic (like skipping steps if unnecessary), running on multiple platforms, and exposing test results/coverage to the system you are running in.

Written properly, actually building the software is the least of what the CI is doing.

If your build is simple enough that you don’t need any of that - great. But pretending that the big CI systems never do anything except lock you in is a trifle simplistic.