Replies: 1 comment 1 reply
-
|
I think you can exclude the default directory if you set |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
MISE_ENValready filters inline TOML tasks viamise.{env}.toml, but file-based scripts under.mise/tasks/are always loaded regardless of environment. This makes it impossible to scope file-based tasks to specific environments (host vs devcontainer, dev vs CI, OS-specific tooling).Of course you can disallow running certain tasks inside the wrong environments by failing and giving the user a warning but it would be nice if
mise tasks lsdoesn't even show the file based tasks which are not applicable to the environment you are running in.In my case my environments are devcontainer or host (since parts of my monorepo are run in either of those two environments) but I have to think this makes sense for CI or other environments.
Rather than creating another directory tree which conflicts with namespacing (i.e. .mise/tasks/devcontainer/task.sh) I think maybe we can add an optional filter to the task's frontmatter that respects the
MISE_ENVsetting like:If you think this makes sense or you have alternative feedback I could make a PR but wanted to ask first.
Beta Was this translation helpful? Give feedback.
All reactions