Replies: 4 comments 4 replies
-
|
NOTE: I managed to roundabout finagle this by utilizing |
Beta Was this translation helpful? Give feedback.
-
|
These might do the trick: https://mise.jdx.dev/configuration/settings.html#auto_install https://mise.jdx.dev/configuration/settings.html#auto_install_disable_tools |
Beta Was this translation helpful? Give feedback.
-
|
There are actually a couple of existing options for this:
That said, a CLI flag is more ergonomic for one-off CI use, so we've added # Skip tool installation
mise run --skip-tools build
# The flag must come before the task name — after the task name it gets passed through as a task argument
mise run build --skip-tools # this passes --skip-tools to the task itselfThis comment was generated by Claude Code. |
Beta Was this translation helpful? Give feedback.
-
|
I have the same challenge. When I want to run a simple linter I don’t need the full blown tool environment. I’m considering using mise tool stubs, still have to experiment with it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a multi-language monorepo setup so a bunch of tools are all present in the repo root
mise.toml. Running any task withmise run ...will install all of those tools.While this is great for local use, however we'd like to use
mise run ...also in CI where it's a bit suboptimal - we'd like to explicitly control what tools get installed in CI while still usingmise runfor re-use between local development and CI scripts.I checked and there's no
--skip-installor similar inmise run --help- perhaps it would be advantageous to add one?Beta Was this translation helpful? Give feedback.
All reactions