(d5a8a3f) Add make check, one command for fmt, clippy and the suite, and bump to 0.32.20
AGENTS.md pins `cargo fmt --check` and `cargo clippy --all-targets` as clean, and 83d31cd is what happens when only memory enforces that: fmt drifted to about 160 places across every file with the tool installed and configured by default the whole time. The decision the ticket wanted, taken: mechanise it, as one command. Not CI, which a single-author tool with no pipeline anywhere does not want, and not a hook, which is a per-clone opt-in the way `blame.ignoreRevsFile` is and so cannot be relied on either. What was missing was never a mechanism, it was one name to type: "remember to run fmt, clippy and the tests" becomes `make check`. Cheapest first, so a formatting slip is reported in a second rather than after the suite. `-D warnings` is what turns clippy's opinion into an exit code, since a warning printed into a wall of cargo output is unread rather than clean. Verified each gate fails on its own: a misformatted function and a `&Vec<u8>` parameter each exit 2 before the tests run. Completions are inside `cargo test` rather than a target of their own. d93eca6 put the check that loads the generated script into a real fish there, so "check tests, check completions" is already one command, and a second target would be a second thing to remember, which is the problem this is solving. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
b63b60eefc
commit
cd7c99fe39
@@ -88,6 +88,17 @@ the command. A pipe holds 64 KiB, so a listing that fits lands in the buffer who
|
||||
and the writer never learns the reader left, giving 0. Only output past that gets far
|
||||
enough to be cut off. Either way nothing is printed to stderr.
|
||||
|
||||
## Checking
|
||||
|
||||
```sh
|
||||
make check # cargo fmt --check, clippy -D warnings, cargo test
|
||||
```
|
||||
|
||||
One command, cheapest first, and the whole of what enforces the formatting and lint rules:
|
||||
there is no CI here and no hook. The completion tests inside it source the generated script
|
||||
into a real fish and ask it what it would offer, so they skip, saying so, on a machine
|
||||
without fish.
|
||||
|
||||
## Releasing
|
||||
|
||||
```sh
|
||||
|
||||
Reference in New Issue
Block a user