From e3e582afefee2b7ffd8f1a5d5f7d0f8d333b1d3e Mon Sep 17 00:00:00 2001 From: lilleman Date: Sat, 4 Jul 2026 09:39:10 +0200 Subject: [PATCH] README: document the one-time org-package-to-repo link for the Packages tab --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 04a803b..9d0fb42 100644 --- a/README.md +++ b/README.md @@ -1194,7 +1194,10 @@ and pushed by that exact commit's branch gate; nothing is rebuilt after merge (b promote by re-tagging). One-time setup: on an account with package write in the `larvit` org, create a Gitea access token with `read:package` + `write:package`, and store the account name as the Actions **variable** `DOCKER_REGISTRY_USER` and the token as the Actions **secret** -`DOCKER_REGISTRY_TOKEN` (a `GITEA_` prefix is rejected — reserved, like `GITHUB_`). Because +`DOCKER_REGISTRY_TOKEN` (a `GITEA_` prefix is rejected — reserved, like `GITHUB_`). The +package is **org-owned** (the image path starts with `larvit/`), so it lists under +`larvit/-/packages`, not the repo — link it once to the repo's Packages tab: +`POST /api/v1/packages/larvit/container/plainpages/-/link/plainpages`. Because this step runs inside the required gate, a missing/expired token (or registry outage) fails every branch's gate and blocks **all** merges until restored — set the secrets before this lands, and use a