From 2284c08aa83be837c11fc8b3a3abb6f30eadb6b9 Mon Sep 17 00:00:00 2001 From: sneak Date: Tue, 29 Sep 2026 01:16:03 +0000 Subject: [PATCH] Say make check needs make bootstrap on a fresh clone (closes #282) The third-party browser assets are not committed, so on a fresh clone make check fails in the tests until make bootstrap (or make assets) has fetched them. The Entrypoints section now says so up front, and why the check does not fetch them itself: it must not change files in the repo. Model: opus-5-5 --- README.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7db1199..5b671a5 100644 --- a/README.md +++ b/README.md @@ -1256,8 +1256,15 @@ standard: normalized scripts in `script/` are the entrypoints for the development workflow. Ten of the Makefile's seventeen targets are thin shims that call them; `build`, `run`, `dev`, `deps`, `clean`, `css` and `version` are inline commands with no script behind them, though -`build` and `version` both take their value from `script/version`. We -provide: +`build` and `version` both take their value from `script/version`. + +`make check` needs the third-party browser assets in `static/`, which +are not committed, so run `make bootstrap` (or just `make assets`) once +after cloning. Without them the tests fail with a message naming that +remedy. `make check` does not fetch them itself because it must not +change any files in the repo. + +We provide: - `script/bootstrap` — install all dependencies (idempotent) - `script/setup` — make a fresh clone ready for development