This repository publishes docs/wiki/ using docs/wiki.yml. The workflow lives at .github/workflows/deploy.yml and uses Deno to check the wiki and build its custom static site.
Pipeline
- Set up Deno and Node.js in GitHub Actions
- Run Deno type-checking, lint, format, test, and docs-wiki audits
deno run -A docs/build.ts --output-dir _site— build the themed static site- Upload
_siteas the Pages artifact deploy-pages— publish
Enable GitHub Pages → Build and deployment → GitHub Actions in repository settings.
Local preview
deno run -A src/wiki/cli.ts -c docs/wiki.yml serve
# http://127.0.0.1:8080/
Build the exact themed Pages output locally with:
deno run -A docs/build.ts --output-dir _site
Custom wikis
For a regular wiki, use wiki build (or deno run -A src/wiki/cli.ts build) and adapt a Pages workflow to:
- pass
-cwith your config path; - set
--site-base-urlto your Pages path (/wiki,/my-wiki, or''for root); - set
pathinupload-pages-artifactto the directory containing the builtindex.html.
The custom docs/build.ts script is specific to this repository's Wikipedia theme. See wiki build for site.url_style, wiki.assets, and collision checks.
Avoid these mistakes
When using upload-pages-artifact and deploy-pages:
- Do not commit
_site/tomain— add_site/to.gitignoreand let CI build the artifact - Do not use Deploy from a branch in Pages settings — use GitHub Actions as the source
- Do not use
peaceiris/actions-gh-pagesor push to agh-pagesbranch for this pattern - Set artifact
pathto the directory that contains the builtindex.html - Use Deno tasks and the Deno-backed CLI; do not install Python, uv, Sphinx, or PyInstaller for the wiki toolchain
- Do not use the removed Python workflow templates; use the Deno workflow template in Wiki Skills
Verify Pages is wired to Actions: gh api repos/{owner}/{repo}/pages --jq '{build_type, source}' should show build_type: workflow.
Agent skill
Coding agents can use Wiki Skills (skills/wiki, deploy reference) to scaffold the workflow and align artifact paths.