nuzlocke-tracker/.beans/nuzlocke-tracker-jlzs--implement-gitea-actions-cicd-pipeline.md

title, status, type, created_at, updated_at, parent

title	status	type	created_at	updated_at	parent
Implement Gitea Actions CI/CD pipeline	draft	task	2026-02-10T09:38:15Z	2026-02-10T09:38:15Z	nuzlocke-tracker-ahza

Set up Gitea Actions as the CI/CD pipeline for the nuzlocke-tracker. Gitea Actions uses the same syntax as GitHub Actions, making it portable if the project goes public on GitHub later.

Context

• Gitea is already running on Unraid behind Nginx Proxy Manager (gitea.nerdboden.de)
• Images are currently built locally and pushed to the Gitea container registry via deploy.sh
• Gitea Actions can automate building, pushing images, and triggering deployment on push to main
• The workflow syntax is compatible with GitHub Actions, so the same .github/workflows/ files work on both platforms

Checklist

• Enable Gitea Actions on the Gitea instance — ensure the Actions feature is enabled in app.ini ([actions] ENABLED = true) and restart Gitea
• Set up a Gitea Actions runner — deploy an act_runner container on Unraid (or the same host as Gitea), register it with the Gitea instance, and verify it picks up jobs
• Create CI workflow (.github/workflows/ci.yml) — on push to develop and PRs: lint, run tests (backend + frontend), and report status
• Create deploy workflow (.github/workflows/deploy.yml) — on push to main: build Docker images (linux/amd64), push to the Gitea container registry, and trigger redeployment on Unraid via SSH
• Configure secrets in Gitea — add repository or org-level secrets for registry credentials, SSH key/host for deployment, and any other sensitive values the workflows need
• Test the full pipeline — push a change through feature/* → develop → main and verify the CI and deploy workflows run successfully end-to-end
• Update deployment docs — document the Gitea Actions setup, how to manage the runner, and how CI/CD fits into the deployment workflow