docs: regenerate installer samples with manifests

testing-guide listed the generated artifacts without derivable.json and
the run samples of wiki/installer.md, and tools.md gave the manifest
command alone. The nightly's commit rules also had no place for the two
files its offline pipeline rewrites, so autorun stopped on them.
This commit is contained in:
Abdessamad Derraz committed 2026-11-06 04:06:45 +01:00
1 parent 78e2b85c1b
commit 548a1bc636
4 files changed
+31 -4

No files matched your search

+5 -2
View File
@@ -463,9 +463,12 @@ refactor: extract shared utils to common.py
Files are staged by name, never with `git add -A` or `git add .`, which sweep in
deletions and work that is not yours. Generated artifacts (`database.json`,
`install/*.json`, `README.md`, `CONTRIBUTING.md`, `exports/`) are committed
`derivable.json`, `install/*.json`, `README.md`, `CONTRIBUTING.md`, `exports/`,
the generated tables and run samples of `wiki/installer.md`) are committed
with the data they derive from, never alone: a manifest committed before the
files it points at gives the installer a 404.
files it points at gives the installer a 404. The run samples count what the
manifests hold, so `generate_installer_doc.py` runs after every manifest
regeneration and its output goes in the same commit.
## CI integration