Tasks can be grouped semantically by using name prefixes separated with :s. For example all testing related tasks may begin with test:. Nested grouping can also be used to further refine groups and simplify pattern matching. For example running mise run test:**:local will matchtest:units:local, test:integration:local and test:e2e:happy:local (See Wildcards for more information).
TIP
Since TOML keys can't contain colons without quoting, use quoted keys in mise.toml:
[tasks."test:unit"] run = 'cargo test --lib'
Do not put embedded scripts in the TOML -- instead
- for platform overall -- put that in 'gpu-offload/scripts'
- for example specific -- put in 'gpu-offload/examples' with some prefix that correlates to the example name
The goal of task ordering is to allow a human to "git clone..." then go through the setup, verification, coding, etc., then teardown -- Utilize "Task Grouping" in mise.toml to assist in that order so when "mise tasks" is execute the human can see the logical order of how to run things -- that means align the alphanumeric sort to accomodat. -- Alwasy prefix the task name with a Alpha -- not a number or symbol -