-
Notifications
You must be signed in to change notification settings - Fork 1.1k
dev: add mise config #6081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev: add mise config #6081
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This currently is missing the documentation update in contributing.md |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| #:schema https://mise.jdx.dev/schema/mise.json | ||
|
|
||
| # NOTE: Tool versions repeat throughout this file. Here's why. | ||
| # ---------- | ||
| # | ||
| # We could use [vars], but they are not supported in task tools: | ||
| # https://github.com/jdx/mise/discussions/4885 | ||
| # | ||
| # We could at least set Rust in [tools], but then it can't be overridden per task. | ||
| # (Another bug?) | ||
| # | ||
| # Finally, adding per-folder [tools] is a bit fragile in general: | ||
| # If 'jj' is itself installed via Mise, any 'jj' invocation will want the tools. | ||
| # And this can easily fail: | ||
| # - "cargo:" tools with unavailable binaries may fail to build on Windows, | ||
| # - a binary might not be available for your OS+architecture, etc. | ||
|
|
||
| [tools] | ||
| # We need cargo-binstall so that Mise would download "cargo:" tools instead of building them. | ||
| "cargo-binstall" = "latest" | ||
|
|
||
| [tasks."format"] | ||
| description = "Format the code" | ||
| tools.rust = "nightly" | ||
| run = "cargo fmt" | ||
|
|
||
| [tasks."lint"] | ||
| description = "Lint the code" | ||
| tools.rust = "1.86" # newer clippy | ||
| run = "cargo clippy --workspace --all-targets --all-features" # TODO: --all-features yay or nay? | ||
|
|
||
| [tasks."zizmor"] | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. suggestion: |
||
| description = "Check GitHub workflows with Zizmor" | ||
| tools.uv = "0.5.1" | ||
| run = "uvx zizmor ." | ||
|
|
||
| [tasks."test"] | ||
| description = "Run tests" | ||
| tools.rust = "1.84" | ||
| tools."cargo:cargo-insta" = "1.42.2" | ||
| tools."cargo:cargo-nextest" = "0.9.93" # TODO: bump to 0.9.94 to get aarch64 on Win | ||
| run = "cargo insta test --workspace --test-runner nextest" | ||
|
|
||
| [tasks."update-cli-help"] | ||
| description = "Update generated CLI help (cli/tests/cli-reference@.md.snap)" | ||
| tools.rust = "1.84" | ||
| tools."cargo:cargo-insta" = "1.42.2" | ||
| run = "cargo insta test --accept --workspace -- test_generate_md_cli_help" | ||
|
|
||
| [tasks."docs:build"] | ||
| description = "Build documentation into rendered-docs/ for offline use" | ||
| tools.uv = "0.5.1" | ||
| run = "uv run mkdocs build -f mkdocs-offline.yml" | ||
|
|
||
| [tasks."docs:serve"] | ||
| description = "Preview documentation with live reloading" | ||
| tools.uv = "0.5.1" | ||
| run = "uv run mkdocs serve" | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I feel like "CI" should go first since it's most important, in some sense.