Documents how a repository opts in to wiki publishing (MIL-006 task 5, issue #60), now that the publisher is a scoped workflow (#62, ADR-0004).
Changes
guides/onboarding.md: new section "Publish a wiki (optional)": enable the wiki, add pages to wiki/, add the marker wiki/.publish (empty = create and update only; the word prune also deletes pages that are not in wiki/), store TOKEN_FOR_GITEA_WIKI in the organization, merge to main. A repository without the marker is skipped and needs no secret.
guides/credentials.md: the wiki secret is per organization with no fallback to TOKEN_FOR_GITEA; the sync token stays read-only; what prune does.
guides/troubleshooting.md: the "no token" row is replaced by the two messages the workflow now prints (TOKEN_FOR_GITEA_WIKI is missing or empty. and the marker-content error); two entries under "Not an error" (no marker; pages kept).
README.md: requirements line, a capability row for wiki publishing (implemented, offline tests, pilot pending), and the "only the first row is implemented" sentence corrected.
Wiki pages changed (rule 8)
English: Home, Onboarding, Credentials, Troubleshooting, Capabilities. Danish and Bahasa Malaysia: the same five (retranslated; the structure test passes). Tests: 144 passed.
Notes
The translations are drafts and not yet reviewed by a native reader (#36).
The scoped publisher ran on main after #62 (run 536, success, 0 created, 0 updated, 0 deleted), so the change of delivery did not alter this repository's wiki.
ADR-0003 still says there is a fallback; marking it superseded in part by ADR-0004 is the RC-018 action item and follows separately.
The capability row says the pilot in a second repository is pending; update it when issue #59 is done.
Documents how a repository opts in to wiki publishing (MIL-006 task 5, issue #60), now that the publisher is a scoped workflow (#62, ADR-0004).
## Changes
- `guides/onboarding.md`: new section "Publish a wiki (optional)": enable the wiki, add pages to `wiki/`, add the marker `wiki/.publish` (empty = create and update only; the word `prune` also deletes pages that are not in `wiki/`), store `TOKEN_FOR_GITEA_WIKI` in the organization, merge to `main`. A repository without the marker is skipped and needs no secret.
- `guides/credentials.md`: the wiki secret is per organization with no fallback to `TOKEN_FOR_GITEA`; the sync token stays read-only; what `prune` does.
- `guides/troubleshooting.md`: the "no token" row is replaced by the two messages the workflow now prints (`TOKEN_FOR_GITEA_WIKI is missing or empty.` and the marker-content error); two entries under "Not an error" (no marker; pages kept).
- `README.md`: requirements line, a capability row for wiki publishing (implemented, offline tests, pilot pending), and the "only the first row is implemented" sentence corrected.
## Wiki pages changed (rule 8)
English: Home, Onboarding, Credentials, Troubleshooting, Capabilities. Danish and Bahasa Malaysia: the same five (retranslated; the structure test passes). Tests: 144 passed.
## Notes
- The translations are drafts and not yet reviewed by a native reader (#36).
- The scoped publisher ran on `main` after #62 (run 536, success, `0 created, 0 updated, 0 deleted`), so the change of delivery did not alter this repository's wiki.
- ADR-0003 still says there is a fallback; marking it superseded in part by ADR-0004 is the RC-018 action item and follows separately.
- The capability row says the pilot in a second repository is pending; update it when issue #59 is done.
Closes #60
Describe the wiki/.publish marker and the prune word, the per-organisation
TOKEN_FOR_GITEA_WIKI without fallback, and the new messages in the
onboarding, credentials and troubleshooting guides and the README. Add the
capability row and regenerate the five English wiki pages with their Danish
and Bahasa Malaysia translations.
Task: MIL-006#5
Tirsvad
merged commit 2dbc2819d4 into main2026-10-10 05:55:13 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Documents how a repository opts in to wiki publishing (MIL-006 task 5, issue #60), now that the publisher is a scoped workflow (#62, ADR-0004).
Changes
guides/onboarding.md: new section "Publish a wiki (optional)": enable the wiki, add pages towiki/, add the markerwiki/.publish(empty = create and update only; the wordprunealso deletes pages that are not inwiki/), storeTOKEN_FOR_GITEA_WIKIin the organization, merge tomain. A repository without the marker is skipped and needs no secret.guides/credentials.md: the wiki secret is per organization with no fallback toTOKEN_FOR_GITEA; the sync token stays read-only; whatprunedoes.guides/troubleshooting.md: the "no token" row is replaced by the two messages the workflow now prints (TOKEN_FOR_GITEA_WIKI is missing or empty.and the marker-content error); two entries under "Not an error" (no marker; pages kept).README.md: requirements line, a capability row for wiki publishing (implemented, offline tests, pilot pending), and the "only the first row is implemented" sentence corrected.Wiki pages changed (rule 8)
English: Home, Onboarding, Credentials, Troubleshooting, Capabilities. Danish and Bahasa Malaysia: the same five (retranslated; the structure test passes). Tests: 144 passed.
Notes
mainafter #62 (run 536, success,0 created, 0 updated, 0 deleted), so the change of delivery did not alter this repository's wiki.Closes #60