News for hackers. Stuff that matters.
Re:The Pain That Is GitHub Actions by LukaD on Thursday March 20, 2025 @11:14AM (#43424515)
> [...] use (shell scripts, make, just, doit, mage, whatever) as long as it is proper, maintainable code

I fully agree with the recommendation to use maintainable code. But that effectively rules out shell scripts in my oppinion. CI shell scripts tend to become big ball of mud rather quickly as you run into the limitations of bash. I think most devs only have superficial knowledge of shell scripts, so do yourself a favor and skip them and go straight to whatever language your team is comfortable with.

Re:The Pain That Is GitHub Actions by sgarland on Thursday March 20, 2025 @07:34PM (#43430270)
Maybe people should get better at shell, instead. Read the bash / zsh manual. Use ShellCheck.
Re:The Pain That Is GitHub Actions by int_19h on Friday March 21, 2025 @12:35AM (#43431880)
Shellcode is just a horrible PL, period. Not only it's weird and unlike anything else out there, there's way too many footguns.

One can learn to use it to the point where it's usable to do advanced automation... but why, when there are so many better options available?

Re:The Pain That Is GitHub Actions by sgarland on Friday March 21, 2025 @08:08AM (#43434661)
Because it’s never going away, and it’s always going to be there. It is the lowest common denominator. Also, a shell script generally doesn’t have any other dependencies (modulo writing one that calls jq or something). No risk of solver hell.