docs(dev): development.md names the wiki: write token scope the mirror needs (#192)
CI / verify (push) Successful in 6m21s
CI / pwsh (push) Successful in 2m21s

Files changed:
- docs/dev/development.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-08 07:08:08 +02:00
1 parent 1a954be65d
commit 765ebe97d7
1 file changed
+6
+6
View File
@@ -217,6 +217,12 @@ job, or to catch up a mirror that failed after its release was published. `ci.ym
resolve fails there rather than at the release. The scripts live under `.gitea/`, which
`dist export` does not copy, so none of this reaches an instance.
Both jobs write with the job token, which needs `permissions: wiki: write` - Gitea gives the wiki
a token scope of its own, and `contents: write` does not cover it (the API answers 403). If the
repository's Actions settings ever cap the token below that, the mirror fails until the cap is
lifted. A wiki that has never had a page has no repository to clone yet; `wiki-push.sh` then
creates the first page through the API and clones afterwards.
### How much of the stack the suite reaches
Coverage is measured in CI - `pytest --cov`, config in `tools/.coveragerc`, HTML and XML