Reference the access-token pictures by their address on main

The publish-wiki workflow publishes the Markdown pages but not wiki/img/, so the nine pictures of AccessTokens returned 404 on the published wiki. The three pages now use raw addresses on main, which resolve once this branch is merged. RC-033 records the finding.
2026-10-13 12:20:09 +08:00
parent 18e30323b4
commit bfe402d217
4 changed files with 33 additions and 32 deletions
@@ -9,7 +9,8 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-13 | Accepted | Jens Tirsvad Nielsen | S02 | Initial version: draft for S02's decision | [9cca295] |
+| 2026-10-13 | Deprecated | Jens Tirsvad Nielsen | S02 | Initial version: draft for S02's decision | [9cca295] |
 | 2026-10-13 | Accepted | Jens Tirsvad Nielsen | S02 | Action item closed: the published wiki did not show the pictures, so the guide references them by their address on `main` | pending |
 ---
@@ -47,7 +48,7 @@ Not covered by this review: the code, the wiki pages and the README are the task
 ## Consequences S02 accepts with a Go
- The wiki pictures are published only if the shared `publish-wiki` workflow copies files other than Markdown. This was not verified here; if it does not, the pictures must be referenced by their address on `main` instead.
+- The shared `publish-wiki` workflow publishes the Markdown pages but not `wiki/img/`: the pictures returned 404 on the published wiki. The three pages therefore reference them by their address on `main` (`raw/branch/main/wiki/img/`), which resolves once the pull request is merged.
 - The pictures keep their English labels in the Danish and Bahasa Malaysia pages.
 ## Overall Verdict
@@ -58,7 +59,7 @@ Go — every criterion of the checklist passes and the changed documents agree w
 | Action | Owner | Due |
 | --- | --- | --- |
-| Check that the published wiki shows the pictures of `AccessTokens`, and fall back to addresses on `main` if it does not | S01 | After the wiki is published |
+| Closed 2026-10-13: the check found the pictures missing and the pages now use addresses on `main`. Open: confirm after the merge that the nine pictures show on the published wiki | S01 | After the merge |
 ---
@@ -1,4 +1,4 @@
-<!-- translation of AccessTokens.md, source sha256 0cf4521af282 -->
+<!-- translation of AccessTokens.md, source sha256 ed97e5f40645 -->
 > Dette er en oversættelse af [`AccessTokens`](AccessTokens). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -40,7 +40,7 @@ Eksemplerne bruger `https://git.tirsystem.com`. Hvis din Gitea kører et andet s
 Log ind på Gitea. Klik på din **avatar** øverst til højre (1), og vælg **Settings** (2).
-![Trin 1: avatarmenuen øverst til højre med Settings fremhævet](img/gitea-1-open-settings.svg)
+![Trin 1: avatarmenuen øverst til højre med Settings fremhævet](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-1-open-settings.svg)
 ### Trin 2. Åbn "Applications"
@@ -48,7 +48,7 @@ Klik på **Applications** (1) i menuen til venstre.
 Du kan også gå direkte dertil: `<din Gitea-adresse>/user/settings/applications`.
-![Trin 2: Applications i venstre menu i indstillingerne](img/gitea-2-applications.svg)
+![Trin 2: Applications i venstre menu i indstillingerne](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-2-applications.svg)
 ### Trin 3. Udfyld token-formularen
@@ -66,7 +66,7 @@ Rul til **Generate New Token** og udfyld den:
 4. Klik på **Generate Token**.
-![Trin 3: token-formularen med navn, adgangsvalg og tre permissions sat til Read and Write](img/gitea-3-token-form.svg)
+![Trin 3: token-formularen med navn, adgangsvalg og tre permissions sat til Read and Write](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-3-token-form.svg)
 > **Opretter du kun projekter i organisationer?** Så kan `user` blive på **Read**. `Read and Write` på `user` er kun nødvendigt for at oprette et repository under din egen konto; uden det svarer Gitea `required=[write:user]`.
@@ -76,7 +76,7 @@ Gitea viser det nye token **én gang**, i en grøn besked øverst på siden (1).
 Hvis du mister værdien, så slet tokenet og opret et nyt.
-![Trin 4: den grønne besked med det nye token og en Copy-knap, og tokenet på listen nedenunder](img/gitea-4-copy-token.svg)
+![Trin 4: den grønne besked med det nye token og en Copy-knap, og tokenet på listen nedenunder](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-4-copy-token.svg)
 ---
@@ -90,13 +90,13 @@ Brug et **klassisk** token. RepoFoundry er ikke testet med fine-grained tokens,
 Log ind på GitHub. Klik på dit **profilbillede** øverst til højre (1), og vælg **Settings** (2).
-![Trin 1: profilmenuen øverst til højre med Settings fremhævet](img/github-1-open-settings.svg)
+![Trin 1: profilmenuen øverst til højre med Settings fremhævet](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-1-open-settings.svg)
 ### Trin 2. Åbn "Developer settings"
 Rul ned i bunden af sidebjælken til venstre, og klik på **Developer settings** (1). Det er det sidste punkt.
-![Trin 2: Developer settings nederst i sidebjælken til venstre](img/github-2-developer-settings.svg)
+![Trin 2: Developer settings nederst i sidebjælken til venstre](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-2-developer-settings.svg)
 ### Trin 3. Vælg "Tokens (classic)"
@@ -106,7 +106,7 @@ Rul ned i bunden af sidebjælken til venstre, og klik på **Developer settings**
 GitHub kan bede dig bekræfte din adgangskode eller en tofaktorkode. Gør det selv; ingen andre bør skrive den.
-![Trin 3: Tokens (classic) i sidebjælken og Generate new token (classic) i knapmenuen](img/github-3-tokens-classic.svg)
+![Trin 3: Tokens (classic) i sidebjælken og Generate new token (classic) i knapmenuen](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-3-tokens-classic.svg)
 > Direkte adresse: `https://github.com/settings/tokens/new`
@@ -126,7 +126,7 @@ GitHub kan bede dig bekræfte din adgangskode eller en tofaktorkode. Gør det se
 4. Rul ned, og klik på **Generate token** (4).
-![Trin 4: formularen til et nyt token med note, udløb, scopet repo afkrydset og knappen Generate token](img/github-4-token-form.svg)
+![Trin 4: formularen til et nyt token med note, udløb, scopet repo afkrydset og knappen Generate token](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-4-token-form.svg)
 > **`read:org` og `admin:org`.** README fastslår, at kontrollen virkede med et token, der havde `repo` og `admin:org`, og at `read:org` alene er utestet. Prøv `read:org` først. `admin:org` giver langt mere magt, end RepoFoundry har brug for, så brug det kun, hvis `read:org` ikke er nok.
@@ -136,7 +136,7 @@ GitHub viser tokenet **én gang**, i en grøn boks øverst (1). Klik på kopiiko
 Hvis ejeren af det nye repository er en organisation, der bruger SAML single sign-on, skal tokenet også godkendes til den organisation: klik på listen over tokens på **Configure SSO** (2) ved tokenet og derefter **Authorize** for organisationen.
-![Trin 5: den grønne boks med det nye token og et kopiikon, og Configure SSO på listen over tokens](img/github-5-copy-token.svg)
+![Trin 5: den grønne boks med det nye token og et kopiikon, og Configure SSO på listen over tokens](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-5-copy-token.svg)
 ---
@@ -47,7 +47,7 @@ the address you set as `GITEA_URL` in `config.env`.
 Sign in to Gitea. Click your **avatar** in the top-right corner (1), then
 choose **Settings** (2).
-![Step 1: the avatar menu in the top-right corner, with Settings highlighted](img/gitea-1-open-settings.svg)
+![Step 1: the avatar menu in the top-right corner, with Settings highlighted](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-1-open-settings.svg)
 ### Step 2. Open "Applications"
@@ -55,7 +55,7 @@ In the menu on the left, click **Applications** (1).
 You can also go straight there: `<your Gitea address>/user/settings/applications`.
-![Step 2: the Applications entry in the left menu of the settings](img/gitea-2-applications.svg)
+![Step 2: the Applications entry in the left menu of the settings](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-2-applications.svg)
 ### Step 3. Fill in the token form
@@ -76,7 +76,7 @@ Scroll to **Generate New Token** and fill it in:
 4. Click **Generate Token**.
-![Step 3: the token form with the name, the access choice and three permissions set to Read and Write](img/gitea-3-token-form.svg)
+![Step 3: the token form with the name, the access choice and three permissions set to Read and Write](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-3-token-form.svg)
 > **Only creating projects in organizations?** Then `user` can stay at **Read**.
 > `Read and Write` on `user` is needed only to create a repository under your
@@ -93,7 +93,7 @@ value again.
 If you lose the value, delete that token and generate a new one.
-![Step 4: the green message with the new token and a Copy button, and the token in the list below](img/gitea-4-copy-token.svg)
+![Step 4: the green message with the new token and a Copy button, and the token in the list below](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-4-copy-token.svg)
 ---
@@ -111,14 +111,14 @@ repository.
 Sign in to GitHub. Click your **profile picture** in the top-right corner (1),
 then **Settings** (2).
-![Step 1: the profile menu in the top-right corner, with Settings highlighted](img/github-1-open-settings.svg)
+![Step 1: the profile menu in the top-right corner, with Settings highlighted](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-1-open-settings.svg)
 ### Step 2. Open "Developer settings"
 In the left sidebar, scroll to the bottom and click **Developer settings** (1).
 It is the last entry.
-![Step 2: Developer settings at the bottom of the left sidebar](img/github-2-developer-settings.svg)
+![Step 2: Developer settings at the bottom of the left sidebar](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-2-developer-settings.svg)
 ### Step 3. Choose "Tokens (classic)"
@@ -131,7 +131,7 @@ It is the last entry.
 GitHub may ask you to confirm your password or a two-factor code. Do that
 yourself; nobody else should type it.
-![Step 3: Tokens (classic) in the sidebar, and Generate new token (classic) in the button menu](img/github-3-tokens-classic.svg)
+![Step 3: Tokens (classic) in the sidebar, and Generate new token (classic) in the button menu](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-3-tokens-classic.svg)
 > Direct address: `https://github.com/settings/tokens/new`
@@ -154,7 +154,7 @@ yourself; nobody else should type it.
 4. Scroll down and click **Generate token** (4).
-![Step 4: the new token form with a note, an expiration, the repo scope ticked and the Generate token button](img/github-4-token-form.svg)
+![Step 4: the new token form with a note, an expiration, the repo scope ticked and the Generate token button](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-4-token-form.svg)
 > **`read:org` and `admin:org`.** The README records that the check worked with
 > a token that had `repo` and `admin:org`, and that `read:org` alone is
@@ -172,7 +172,7 @@ sign-on, the token must also be authorised for that organization: in the token
 list click **Configure SSO** (2) next to the token and then **Authorize**
 for the organization.
-![Step 5: the green box with the new token and a copy icon, and Configure SSO in the token list](img/github-5-copy-token.svg)
+![Step 5: the green box with the new token and a copy icon, and Configure SSO in the token list](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-5-copy-token.svg)
 ---
@@ -1,4 +1,4 @@
-<!-- translation of AccessTokens.md, source sha256 0cf4521af282 -->
+<!-- translation of AccessTokens.md, source sha256 ed97e5f40645 -->
 > Ini ialah terjemahan [`AccessTokens`](AccessTokens). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -40,7 +40,7 @@ Contoh menggunakan `https://git.tirsystem.com`. Jika Gitea anda berada di tempat
 Log masuk ke Gitea. Klik **avatar** anda di penjuru kanan atas (1), kemudian pilih **Settings** (2).
-![Langkah 1: menu avatar di penjuru kanan atas dengan Settings ditonjolkan](img/gitea-1-open-settings.svg)
+![Langkah 1: menu avatar di penjuru kanan atas dengan Settings ditonjolkan](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-1-open-settings.svg)
 ### Langkah 2. Buka "Applications"
@@ -48,7 +48,7 @@ Dalam menu di sebelah kiri, klik **Applications** (1).
 Anda juga boleh terus ke sana: `<alamat Gitea anda>/user/settings/applications`.
-![Langkah 2: entri Applications dalam menu kiri tetapan](img/gitea-2-applications.svg)
+![Langkah 2: entri Applications dalam menu kiri tetapan](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-2-applications.svg)
 ### Langkah 3. Isi borang token
@@ -66,7 +66,7 @@ Tatal ke **Generate New Token** dan isikannya:
 4. Klik **Generate Token**.
-![Langkah 3: borang token dengan nama, pilihan akses dan tiga permission ditetapkan kepada Read and Write](img/gitea-3-token-form.svg)
+![Langkah 3: borang token dengan nama, pilihan akses dan tiga permission ditetapkan kepada Read and Write](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-3-token-form.svg)
 > **Hanya mencipta projek dalam organisasi?** Maka `user` boleh kekal pada **Read**. `Read and Write` pada `user` hanya diperlukan untuk mencipta repositori di bawah akaun anda sendiri; tanpanya Gitea menjawab `required=[write:user]`.
@@ -76,7 +76,7 @@ Gitea menunjukkan token baharu **sekali sahaja**, dalam mesej hijau di bahagian
 Jika anda kehilangan nilai itu, padam token tersebut dan jana yang baharu.
-![Langkah 4: mesej hijau dengan token baharu dan butang Copy, serta token dalam senarai di bawah](img/gitea-4-copy-token.svg)
+![Langkah 4: mesej hijau dengan token baharu dan butang Copy, serta token dalam senarai di bawah](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/gitea-4-copy-token.svg)
 ---
@@ -90,13 +90,13 @@ Gunakan token **klasik**. RepoFoundry belum diuji dengan token fine-grained, ker
 Log masuk ke GitHub. Klik **gambar profil** anda di penjuru kanan atas (1), kemudian **Settings** (2).
-![Langkah 1: menu profil di penjuru kanan atas dengan Settings ditonjolkan](img/github-1-open-settings.svg)
+![Langkah 1: menu profil di penjuru kanan atas dengan Settings ditonjolkan](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-1-open-settings.svg)
 ### Langkah 2. Buka "Developer settings"
 Dalam bar sisi kiri, tatal ke bahagian bawah dan klik **Developer settings** (1). Ia ialah entri terakhir.
-![Langkah 2: Developer settings di bahagian bawah bar sisi kiri](img/github-2-developer-settings.svg)
+![Langkah 2: Developer settings di bahagian bawah bar sisi kiri](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-2-developer-settings.svg)
 ### Langkah 3. Pilih "Tokens (classic)"
@@ -106,7 +106,7 @@ Dalam bar sisi kiri, tatal ke bahagian bawah dan klik **Developer settings** (1)
 GitHub mungkin meminta anda mengesahkan kata laluan atau kod dua faktor. Lakukannya sendiri; tiada orang lain patut menaipnya.
-![Langkah 3: Tokens (classic) dalam bar sisi, dan Generate new token (classic) dalam menu butang](img/github-3-tokens-classic.svg)
+![Langkah 3: Tokens (classic) dalam bar sisi, dan Generate new token (classic) dalam menu butang](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-3-tokens-classic.svg)
 > Alamat terus: `https://github.com/settings/tokens/new`
@@ -126,7 +126,7 @@ GitHub mungkin meminta anda mengesahkan kata laluan atau kod dua faktor. Lakukan
 4. Tatal ke bawah dan klik **Generate token** (4).
-![Langkah 4: borang token baharu dengan nota, tarikh luput, skop repo ditandakan dan butang Generate token](img/github-4-token-form.svg)
+![Langkah 4: borang token baharu dengan nota, tarikh luput, skop repo ditandakan dan butang Generate token](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-4-token-form.svg)
 > **`read:org` dan `admin:org`.** README mencatatkan bahawa semakan itu berjaya dengan token yang mempunyai `repo` dan `admin:org`, dan bahawa `read:org` sahaja belum diuji. Cuba `read:org` dahulu. `admin:org` memberi kuasa jauh lebih banyak daripada yang diperlukan RepoFoundry, jadi gunakannya hanya jika `read:org` tidak mencukupi.
@@ -136,7 +136,7 @@ GitHub menunjukkan token **sekali sahaja**, dalam kotak hijau di bahagian atas (
 Jika pemilik repositori baharu ialah organisasi yang menggunakan SAML single sign-on, token juga mesti dibenarkan untuk organisasi itu: dalam senarai token, klik **Configure SSO** (2) di sebelah token dan kemudian **Authorize** untuk organisasi.
-![Langkah 5: kotak hijau dengan token baharu dan ikon salin, serta Configure SSO dalam senarai token](img/github-5-copy-token.svg)
+![Langkah 5: kotak hijau dengan token baharu dan ikon salin, serta Configure SSO dalam senarai token](https://git.tirsystem.com/TirSystem-BashScript/repo-foundry/raw/branch/main/wiki/img/github-5-copy-token.svg)
 ---