Harden registry credentials in workflow
This commit is contained in:
@@ -36,9 +36,11 @@ Gitea Actions workflow: `.gitea/workflows/ci.yml`
|
||||
|
||||
Required repository or organization secrets:
|
||||
|
||||
- `REGISTRY_USERNAME`: Gitea username allowed to publish packages
|
||||
- `REGISTRY_PASSWORD`: Gitea personal access token with package read/write access
|
||||
- `REGISTRY_IMAGE`: full image name, for example `gitea.reversed.dev/space/evil-wordle`
|
||||
- `REGISTRY_USERNAME`: optional; defaults to the Gitea Actions actor
|
||||
- `REGISTRY_IMAGE`: optional; defaults to `gitea.reversed.dev/space/evil-wordle`
|
||||
|
||||
The workflow also accepts `REGISTRY_TOKEN` as a fallback for `REGISTRY_PASSWORD`.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user