Do you have so much #bash in your #gitlab pipelines that you wish you could use professional tooling, IDEs, shellcheck, local execution, etc.?
Well, have I got a tool for you. Compile your .sh files into yaml.
Do you have so much #bash in your #gitlab pipelines that you wish you could use professional tooling, IDEs, shellcheck, local execution, etc.?
Well, have I got a tool for you. Compile your .sh files into yaml.
--
- "How are we linting our #bash when it is wrapped in #yaml?"
- "Sometimes there isn't a convenient way to not put the bash into yaml."
Okay, Assistant wrote this- extracts bash & sends it to a linter. So much more to this left to do.
Why did we ever put bash into yaml?
---
This is my annual attempt to write bash that has loops.
Why do I do it?:
- Self hatred?
- Create motivation to finally learn #zsh/#fish (or even #xonsh)?
- I'd forgotten that loops are trash in #bash?
- prelude to just doing it all in #python?
(updated, tagging 5 communities so that they can all fight with me in the replies and the pet fish owners can be confused)
if-blocks, while-blocks and their test expressions in #bash are syntactic bitters