space/evil-wordle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use explicit Gitea registry credentials
Some checks are pending
test-build-publish / docker (push) Has started running
Details

Browse Source
This commit is contained in:
Space-Banane
2026-05-14 18:35:41 +02:00
parent 5b442b09f5
commit 76e6ced205
2 changed files with 19 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -37,11 +37,13 @@ Gitea Actions workflow: `.gitea/workflows/ci.yml`
Required repository or organization secrets:
- `REGISTRY_PASSWORD`: Gitea personal access token with package read/write access
- `REGISTRY_USERNAME`: optional; defaults to the Gitea Actions actor
- `REGISTRY_USERNAME`: Gitea username that owns the token
- `REGISTRY_IMAGE`: optional; defaults to `gitea.reversed.dev/space/evil-wordle`
The workflow also accepts `REGISTRY_TOKEN` as a fallback for `REGISTRY_PASSWORD`.
For organization packages such as `space/evil-wordle`, the username is still the actual Gitea user account for the token, not the organization name. That user needs permission to publish packages under `space`.
The workflow uses `catthehacker/ubuntu:act-latest`, Docker Buildx, and links the published package back to the `space/evil-wordle` repository through the Gitea API.
On pushes to `main`, CI publishes: