It's really easy to learn - about an afternoon to peruse the docs. And quite capable.
It's really easy to learn - about an afternoon to peruse the docs. And quite capable.
Of course, if those aren't dynamics you have to deal with, definitely go with what works.
There's also invoke (https://www.pyinvoke.org/). I suspect it too is more powerful than just, and I know teams that use them.
just supports the same. If you begin a recipe with a shebang (#!/bin/bash), then it dumps the whole recipe to a file and executes it as a shell script.
Not limited to bash - you can do the same with Python, etc.
As for scripts in their own files vs embedded in a justfile: I've noticed people's opinions vary. Even in my team we'd debate the issue. I prefer them in the justfile so I can read them in one place - as long as it's not huge. Some team members preferred them in their own files.
The own-file bit comes in nice when you want to run them standalone (CI/CD; maybe someone doesn’t want to use the runner) or you’re fighting against escaping rules. I like having them in the mise file when they’re just a couple of lines. If it turns into a full-on thing, then I prefer to extract it.
Either way, options are nice.