haylanandClaude-Bot
1d15d6950f
Gitea packages belong to the owner, not a repo, by default — pushing alone doesn't surface the image under this repo's Packages tab, and the org.opencontainers.image.source label some workflows set for this doesn't auto-link on Gitea (closed feature request, never implemented). Call the link API explicitly after push instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
godot-ci
Custom image extending barichello/godot-ci:4.7.1 with the Godot 4.7.1 export-template toolchain
pre-installed, so Project4x's export-template.yml doesn't apt-get install it on every release
run.
Built from the handoff spec at Project4x's docs/handoff/godot-ci-custom-image.md.
Image
git.arthurerlich.de/haylan/godot-ci:4.7.1
Published automatically by .gitea/workflows/publish.yml on every push to main that touches
Dockerfile, or manually via workflow dispatch.
A Godot version bump means updating Dockerfile's FROM line and the tag in both the workflow
and this README together.
Auth
The publish workflow pushes to this repo's Gitea package (container) registry using a Personal
Access Token stored as the repo secret REGISTRY_PUSH_PAT — the built-in per-run GITEA_TOKEN
cannot push to the package registry on this instance.
- Scope:
write:package(read:packagetoo if the workflow ever needs to pull the image back before tagging). - Owner: TODO — fill in once the token is generated (Settings → Applications → Generate New Token on the account that should own the published packages).
Consuming this image
In Project4x's .gitea/workflows/export-template.yml:
- container: barichello/godot-ci:4.7.1
+ container: git.arthurerlich.de/haylan/godot-ci:4.7.1