Taskfile
scripts-to-rule-them-all
Taskfile | scripts-to-rule-them-all | |
---|---|---|
5 | 8 | |
325 | 3,140 | |
- | - | |
0.0 | 0.0 | |
5 months ago | over 1 year ago | |
Shell | Shell | |
- | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Taskfile
- Shell Taskfile
-
What’s with DevOps engineers using `make` of all things?
https://github.com/adriancooney/Taskfile - my favourite for its simplicity. A shell alias and a shell script with a function for each "job". No need to learn yet another tool when you just want to run a few pre-defined commands from a project's root. I think, if you're going to complain about make, then maybe all you really need is a shell script.
- Alternatives to Makefile for Python
-
How a true gentleman navigate in Linux or Unix terminal...
You want to use $@ rather than $* so you don't have to do double-quoting on arguments that have spaces in them. That said, I'm gonna steal this. Also if you like clever composability tricks check out Taskfiles, I've adopted them all over in my own code.
-
I Prefer Makefiles over Package.json Scripts
I was amazed to discover Taskfile. Didn't realise it was a copy of Make.
https://github.com/adriancooney/Taskfile
scripts-to-rule-them-all
-
What’s with DevOps engineers using `make` of all things?
Personally I like https://github.blog/2015-06-30-scripts-to-rule-them-all/ as a pattern and then let the authors do whatever crazy thing they want from there. In my experience, 99% of repos never move past using simple shell scripts with a few common functions with that pattern, and things are kept fairly simple. A select few repositories tend to mature enough that they are able to invest in swapping towards something more testable than shell scripts, and then you just have a couple people who stick to invoking `make` from the scripts but it's fine and nobody has to think about it except them. We don't stick to that exact set of scripts, but find that as long as you don't use more than like 10ish entrypoints in `script/*`, and have at least `script/bootstrap` it's fine.
- Scripts to Rule Them All (2015)
-
Just: A Command Runner
I dig the general idea, but question the value add over a directory of `scripts` that follow sane conventions (ie `script/test`, `script/build` etc). Is the main thing that you can do `just -l` to see available commands? I have never really reached for `make` when I've had a choice, as I've done mostly ruby, JS, or java where you have more sane, humane tools (i.e. Rake, Yarn, Maven though that one is never fun).
My general approach is every repo should have something that follows https://github.com/github/scripts-to-rule-them-all, written in sh (maybe bash, its 2023), linted with shellcheck. When you need something fancy Rake is great or grab some nice bash command line helper and source it from all your scripts. Is a command listing really worth another dependency over what you get from `ls script` or `cat script/README` ?
- [AskJS] What is the best way to create a common npm package for building others?
-
Azure Pipeline running task in background?
Afaik AzDo cannot run tasks concurrently. From having had to work with azure pipelines I would highly suggest to use the github approach of Scripts to rule them all and avoiding predefined tasks unless absolutely necessary(Things that are complicated to implement and solutions already existing.
-
Why is uncoupled documentation bad?
GitHub have a pattern for this called "scripts to rule them all" - https://github.com/github/scripts-to-rule-them-all - I've not fully adopted it yet but I probably should, it looks very well thought-out.
-
Script up your projects
People at Github made an attempt to fix this situation: scripts to rule them all. The idea is to have common set of executable scripts for common developer tasks in a script/ directory in the root of every project:
-
How to Join a Team and Learn a Codebase
https://github.com/github/scripts-to-rule-them-all
What are some alternatives?
just - 🤖 Just a command runner
govuk_design_system_formbuild
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
django-sql-dashboard - Django app for building dashboards using raw SQL queries
Task - A task runner / simpler Make alternative written in Go
govuk-form-builder - A form builder for Ruby on Rails that’s compatible with the GOV.UK Design System.
magicfile - Simple Makefile template for documenting frequent commands.
generate-package - Use as a sub-generator or plugin in your generator to create a package.json for a project. Or install globally and run with Generate's CLI.
tup - Tup is a file-based build system.
pure-sh-bible - 📖 A collection of pure POSIX sh alternatives to external processes.
npm
confgen - Generate repetitive configs for vite, typescript, eslint, etc