CI: log in to the registry as the repository owner #4

Merged
branderson merged 1 commits from ci-registry-login into main 2026-10-13 23:19:13 -07:00
2 changed files with 6 additions and 7 deletions
+3 -3
View File
@@ -1,8 +1,8 @@
# Builds the app, session manager and streamer images and pushes them to this
# Gitea instance's container registry, under the repository's owner.
#
# Needs repository secrets REGISTRY_USERNAME and REGISTRY_TOKEN: a user, and an
# access token of theirs with package write access.
# Needs a repository secret REGISTRY_TOKEN: an access token with package write
# access, belonging to the repository's owner.
name: Images
on:
@@ -46,7 +46,7 @@ jobs:
- uses: docker/login-action@v3
with:
registry: ${{ steps.registry.outputs.host }}
username: ${{ secrets.REGISTRY_USERNAME }}
username: ${{ github.repository_owner }}
password: ${{ secrets.REGISTRY_TOKEN }}
- id: meta
+3 -4
View File
@@ -45,10 +45,9 @@ pushes them to the Gitea instance's container registry, under the repository's
owner. Pushes to `main` publish a `main` tag; `v1.2.3` tags publish `1.2.3`,
`1.2` and `latest`. Its jobs run docker builds, so they need a runner labelled
`dejima-privileged`; jobs that don't build images should use `dejima-confined`.
It also needs two repository secrets:
- `REGISTRY_USERNAME`: a user;
- `REGISTRY_TOKEN`: an access token of theirs with package write access.
It also needs a repository secret, `REGISTRY_TOKEN`: an access token with
package write access, belonging to the repository's owner, whom the workflow
logs in as.
## Volumes