docs: bug-report instruction offers WIKI_TRACE=1 for a reproduction (#157)
CI / verify (push) Successful in 2m1s
Release / release (push) Successful in 38s

Files changed:
- CHANGES.md
- VERSION
- instructions/bug-report.md
This commit is contained in:
torben committed 2026-09-30 17:30:11 +02:00
1 parent f9c047bd2e
commit 4f0622dfa4
3 files changed
+6 -2

No files matched your search

+3
View File
@@ -122,6 +122,9 @@ Facts only: no page content, no guessed cause, no advice.
## Decision points
- **The user declines the trace?** Run with `--no-trace`. The manifest records the exclusion.
- **The failure can be reproduced, and there is no trace?** A distributed instance records none by
default. Offer to repeat the failing step in one new shell with `WIKI_TRACE=1` set for that
session only, then collect. Do not change the checkout's telemetry configuration for it.
- **The user wants the report to name pages?** Run with `--titles`; the bundle then also carries
`tree-paths.txt`, which lists every path under `kb/` and `raw/`.
- **The collector exits 1?** It could not write the bundle (a missing input file, a full disk). Read