docs: bug-report instruction step 1 no longer calls every bundle unpseudonymised (#158)
CI / verify (push) Successful in 2m13s
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 20:16:53 +02:00
1 parent 76d67e45ba
commit 08dde007dd
3 files changed
+11 -4

No files matched your search

+8 -1
View File
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
---
## 8.0.0-beta.8 - 2026-09-30 - Bug-report collector can pseudonymise identities, in two stages
## 8.0.0-beta.9 - 2026-09-30 - bug-report instruction: step 1 no longer calls every bundle unpseudonymised
**Author:** Torben Nehmer
@@ -113,8 +113,15 @@ concern - readable here, never shipped as something to parse.
- Demo corpus follows the decided project pages: three states, seed with their items (#156)
- bug-report instruction: offer WIKI_TRACE=1 for a reproduction
- reports/CONTRACT.md: only the collector's two counting calls take the bugreport session id
- bug-report instruction: step 1 no longer calls every bundle unpseudonymised
<!-- /wikitool:bumps -->
### bug-report instruction: step 1 no longer calls every bundle unpseudonymised
Step 1 told the agent to announce that the bundle "is not pseudonymised" and then, one paragraph
later, to offer `--pseudonymise`. It now says the bundle holds machine, user and path names and the
git remotes unless it is pseudonymised.
### Bug-report collector can pseudonymise identities, in two stages (Gitea #158)
A bundle carries machine, user and path names, and an installation failure usually turns on the
+1 -1
View File
@@ -1 +1 @@
8.0.0-beta.8
8.0.0-beta.9
+2 -2
View File
@@ -82,8 +82,8 @@ session. The bundle does not leave that place because of it.
## Steps
1. **Tell the user what is about to happen**, in the instance's KB language: a bundle will be written
under `reports/`, it is not pseudonymised, it holds machine, user and path names and the git
remotes, and it is not sent anywhere. Ask whether the session trace, page titles and transcripts
under `reports/`, it holds machine, user and path names and the git remotes unless it is
pseudonymised (below), and it is not sent anywhere. Ask whether the session trace, page titles and transcripts
may go in. The defaults are: trace in, titles out, no transcripts.
Ask which channel the bundle will take, and recommend pseudonymisation for every channel except a