fixing wiki generation some more (#39)
Generate and publish developer Wiki / validate-wiki (push) Successful in 7s
Build and publish release / create-release (push) Successful in 1m4s
Build and publish release / build (push) Failing after 31m41s
Build and publish release / publish-release (push) Skipped
Generate and publish developer Wiki / publish-wiki (push) Successful in 11s
Build and publish release / metadata (push) Successful in 50s

Reviewed-on: #39
Co-authored-by: Koda YeenBean <n122330@gmail.com>
This commit was merged in pull request #39.
This commit is contained in:
2026-07-19 22:48:38 +01:00
committed by Koda
parent 4f30a031bb
commit 21dda2e618
2 changed files with 33 additions and 12 deletions
+6 -3
View File
@@ -71,9 +71,12 @@ so both run natively on ARM and x86 build agents.
Publishing is an explicit authenticated step: `./scripts/docs/publish-wiki.sh`.
The script derives the lowercase `.wiki.git` repository URL from `origin`,
checks it out before generating, and accepts an explicit URL override. No
credentials are stored in this repository. The documentation workflow performs
the same two-checkout process and requires `GITEA_TOKEN` to have write access to
`Koda/openunifi.wiki`.
credentials are stored in this repository. The documentation workflow clones the
Wiki Git endpoint directly because it is not a normal API repository. Its
publishing job requests Gitea's `wiki: write` permission for `GITEA_TOKEN` and
passes the token through a transient HTTP authentication header. Repository
Actions settings must allow Wiki write access because Gitea clamps requested
job permissions to the configured maximum.
## Automated releases