From 60910f7b23415a82c3a2da808d88aa5409d0262e Mon Sep 17 00:00:00 2001 From: Jeffery Date: Mon, 24 Aug 2026 18:54:19 +0800 Subject: [PATCH] =?UTF-8?q?docs(wiki):=20=E8=A3=9C=E4=B8=8A=20wiki=20?= =?UTF-8?q?=E9=80=A3=E7=B5=90=E7=9A=84=E6=96=B9=E5=90=91=E8=88=87=E4=BD=9C?= =?UTF-8?q?=E7=94=A8=E7=AF=84=E5=9C=8D=E8=A6=8F=E7=AF=84?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 1 + skills/wiki/SKILL.md | 16 ++++++++++++++++ 2 files changed, 17 insertions(+) diff --git a/README.md b/README.md index d51c985..71029b3 100644 --- a/README.md +++ b/README.md @@ -32,6 +32,7 @@ gitea.sh wiki-repo # 解析頁面類型的 wiki gitea.sh wiki-list / gitea.sh wiki-get / # 不存在 exit 4 gitea.sh wiki-put / # 自動判斷新建或更新 +gitea.sh wiki-url / # 印出 wiki 頁絕對網址（取自 API 的 html_url）；跨存取庫連結用 gitea.sh pr-create / <body-file> gitea.sh api <METHOD> <path> [json-file] hash-id <text> # 與 gitea.sh hash-id 相同 diff --git a/skills/wiki/SKILL.md b/skills/wiki/SKILL.md index 8be55d4..5b8d7dd 100644 --- a/skills/wiki/SKILL.md +++ b/skills/wiki/SKILL.md @@ -22,6 +22,22 @@ Different page types can live in different `{owner}/{repo}` repos, classified by | list pages | `tools/gitea.sh wiki-list {owner}/{repo}` | | read page | `tools/gitea.sh wiki-get {owner}/{repo} {page}` (exit 4 when missing) | | write page | write the content to a temp file first, then `tools/gitea.sh wiki-put {owner}/{repo} {page} {file}` (creates or updates automatically) | +| page URL | `tools/gitea.sh wiki-url {owner}/{repo} {page}` — the page's absolute URL, taken from the API's `html_url` (exit 4 when the page is missing) | + +## Linking between wiki pages + +Two rules, and getting either wrong produces a link that silently points at a page that does not exist. + +**Direction**: Gitea uses the GitHub/Gollum convention — `[[display text|page name]]`, **display text on the LEFT, page name on the RIGHT**. This is the opposite of MediaWiki. Gitea's own source says so (`modules/markup/html_link.go`): *"MediaWiki uses [[link|text]], while GitHub uses [[text|link]] … we prefer GitHub syntax"*. So `[[PLAN_H1234567|我的計畫]]` renders as the text `PLAN_H1234567` linking to a page named 我的計畫 — broken. Write `[[我的計畫|PLAN_H1234567]]`. When display text and page name are the same, use the no-pipe form `[[PLAN_H1234567]]`, which cannot be got wrong. + +**Scope**: `[[...]]` and relative markdown links both resolve **only inside the current wiki**. There is no cross-repo wiki-link syntax. + +| Link | Same wiki? | Use | +| --- | --- | --- | +| Same page type (e.g. `PLAN_CONTENTS` → `PLAN_{HASH}`) | Always — one type, one repo | `[[display\|page]]` or `[[page]]` | +| Different page type (e.g. `LOG_{HASH}` → `PLAN_{HASH}`) | **Only when both types resolve to the same repo** | Absolute URL from `wiki-url`: `[display](https://…/wiki/PLAN_…)` | + +Because each type resolves its own `JSC_WIKI_REPO_{TYPE}`, a cross-type link **must** use the absolute URL — it stays correct whether or not the two types happen to share a repo, so never branch on that. Get the URL from `wiki-url`, never hand-assemble the path. ## Rules