Open notnmeyer opened 3 weeks ago
another option could be to extend --filter <regex>
to also support running tasks, like, tsk --filter <regex>
. maybe in that case the previous command displays a list of what would run, and then you have to confirm it with, task --filter <regex> --run
?
meh
something like,
it would help keep the the task count down on more complex stuff, or in monorepos. no need for a "build-all" task in this case.
should we enforce a particular order when running them (alphabetically)? or should they run in parallel?
probably shouldnt have regex support, seems too scary to accidentally a task you didn't mean to