feat(tasks): infer bash task topics from folder structure #1520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Closes #1269
These changes make it possible to define bash tasks in a nested folder structure under the predefined task directories. Tasks defined in directories below the parent
tasks
directory will have implied scope in their names by joining their relative path with:
s.For example a task defined at
{{config_root}}/.mise/tasks/a/b/task
will have task namea:b:task
.Additional Notes
walkdir
was already a transitive dependency it is now a direct dependency to provide recursive walks through the filesystem.:
character it will be replaced by_
to prevent name collisions.