Wiki repos are sibling `.wiki` git repos — workflow note #13

New issue

Open

opened 2026-07-21 22:20:14 +00:00 by agent · 0 comments

agent commented

2026-07-21 22:20:14 +00:00

Member

Observation

Forgejo wikis are not accessible via the REST API on our instance (all /api/v1/.../wiki/... endpoints return 404). However, wikis are available as separate git repos using the .wiki suffix.

Verified behavior

For any repo git.merith.xyz/residual/<repo>, the wiki is at:

Git URL: https://git.merith.xyz/residual/<repo>.wiki.git
SSH URL: ssh://git@git.merith.xyz:3022/residual/<repo>.wiki.git

Example: residual/.agent → residual/.agent.wiki.git

Implications for workflow

If we want to integrate wikis into the agent workflow:

Clone .wiki repos alongside their parent repos
Wiki pages are markdown files in the repo root
Standard git operations (add/commit/push) apply
The .agent/tools/common.sh repo discovery would need to handle .wiki repos if we want them synced

No action required now

This is an informational note for future reference. No implementation work is planned unless we decide to use wikis for user guides, roadmaps, or operational notes.

Forgejo version: 16.0.0+gitea-1.22.0
Wiki API status: disabled/unavailable (returns 404 on all endpoints)
Wiki git access: confirmed working (repo exists and is cloneable)

## Observation Forgejo wikis are not accessible via the REST API on our instance (all `/api/v1/.../wiki/...` endpoints return 404). However, wikis **are** available as separate git repos using the `.wiki` suffix. ## Verified behavior For any repo `git.merith.xyz/residual/<repo>`, the wiki is at: - **Git URL:** `https://git.merith.xyz/residual/<repo>.wiki.git` - **SSH URL:** `ssh://git@git.merith.xyz:3022/residual/<repo>.wiki.git` Example: `residual/.agent` → `residual/.agent.wiki.git` ## Implications for workflow If we want to integrate wikis into the agent workflow: - Clone `.wiki` repos alongside their parent repos - Wiki pages are markdown files in the repo root - Standard git operations (add/commit/push) apply - The `.agent/tools/common.sh` repo discovery would need to handle `.wiki` repos if we want them synced ## No action required now This is an informational note for future reference. No implementation work is planned unless we decide to use wikis for user guides, roadmaps, or operational notes. ## Related - Forgejo version: `16.0.0+gitea-1.22.0` - Wiki API status: disabled/unavailable (returns 404 on all endpoints) - Wiki git access: confirmed working (repo exists and is cloneable)