Add mise.toml#61
Conversation
|
@copilot use mise from GitHub action including preview auto install Omit just fmt. Simplify commands like by making reasonable assumptions like non empty git ls-files output, and using builtin file finding where available. Comment on prettier-write that we want to use it for everything except markdown because it adds too much vertical whitespace. |
Done in 778f35f:
Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
covracer
left a comment
There was a problem hiding this comment.
Use MIS in place of FORCEREDDY and PCAM. Also omit quotes in YAML where possible.
|
How do I unblock the GitHub Actions network failures? Similar to manual stage hook classification but inverted, make a pre-commit-fast task, and rename existing to pre-commit-all Omit captain obvious descriptions. Only leave comments or descriptions explaining why some hooks aren't in the fast collection (slow or need Internet). Prefer single quotes for less visual noise. |
|
@copilot see above Also I added jdx.dev to allowlist |
Done in ef81371:
Done in ef81371: added
The |
All inline review comments addressed in 87b13d1. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot see comments |
6f95de6 to
9add2ed
Compare
9add2ed to
6c0dbb5
Compare
mise combines asdf-style tool versioning, justfile-style task running, and — as an experiment — pre-commit hook orchestration in one
.toml. This PR begins that migration, including building replacements tosummarize, which can end up showing two tables in GitHub Actions, with more specializedmise run tabularizeandmise run set-environment.Background and Links
installtask and apre-committask suite mirroring.pre-commit-hooks.yamluv_venv_auto = 'create|source'for auto-creating and sourcing the venv on directory entryChanges and Testing
basedpyrightfrom PyPI instead of the NPM registryQuestions and Followup
uvandnpm, are we specifying tool versions, installing as needed, setting $PATH, and running as simply and reliably as possible?mise run-on-sourcesreinventing the wheel?