larvit/plainpages
3
0
Fork 0
Code Issues 1 Pull Requests 3 Actions 4 Packages Projects Releases Wiki Activity

README: document the one-time org-package-to-repo link for the Packages tab #7

Merged
lilleman merged 1 commits from readme-package-link into main 2026-07-04 09:42:23 +02:00
Conversation 0 Commits 1 Files Changed 1
+4 -1
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit e3e582afef - Show all commits
README.md
+4 -1
View File
@@ -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