coulomb/shard-wiki
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

research: git-forge wikis deep dive (Gitea/GitLab/GitHub); UC-76-77

Browse Source 
SHARD-WP-0003 T5. The home case: a forge wiki is a separate .wiki.git repo of
Markdown -> page model, history, coordination journal map 1:1 with near-zero
adapter. git-clone universal across all three; wiki content API
capability-varying (GitLab/Gitea yes, GitHub git-only). git IS the canonical
store (not a mirror), so write-by-commit is safe -- resolves the UC-68/Q22
race for this case. UC-76 (clone .wiki.git attach), UC-77 (forge wiki API,
capability varies). Enriched UC-40/02/68/38. Marks T5 done.
Feeds SHARD-WP-0002 T14/T11.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-06-14 19:40:46 +02:00
parent 31ec8ab205
commit dbc42f05db
7 changed files with 272 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
research/260614-forge-wikis-deep-dive/README.md Normal file
View File

@@ -0,0 +1,17 @@
# 260614 — git-forge wikis deep dive (Gitea · GitLab · GitHub)
Deep dive on the **git-forge-hosted Markdown wikis** as one grouped memo: each is a
**dedicated git repository of Markdown** exposed through a forge, attachable by **cloning
the wiki repo directly** *or* (where offered) through the **forge's wiki API**. INTENT names
**Gitea wikis** explicitly as a shard participant — this dive confirms the **git-native
file-store** as a first-class, and the *simplest*, backend.
- `findings.md` — the three forges compared, the `.wiki.git` model, API matrix, capability
profile, INTENT mapping, UC seeds (UC-76/77), architecture notes for SHARD-WP-0002, open
questions (resolves the UC-68 source-of-truth question for this case), sources,
traceability.
Catalog yield: UC-76 (attach a forge wiki by cloning its dedicated `.wiki.git` — git **is**
the native store and the coordination journal), UC-77 (attach/write via the forge wiki API
where git-clone is unavailable/undesired — capability varies by forge). Enriched
UC-40/02/68/38. Feeds SHARD-WP-0002 T14 (attachment binding).