claude-memory/graph/configurations/gitea-actions-shared-composite-actions-repo-pattern-73646e.md

id	type	title	tags	importance	confidence	created	updated
73646e80-a640-4316-b7c6-54a4330f1b28	configuration	Gitea Actions shared composite actions repo pattern	gitea ci-cd actions workflow convention docker	0.8	0.8	2026-02-18T20:06:25.840515+00:00	2026-02-18T20:06:25.840515+00:00

All CI/CD workflows across projects use shared composite actions from cal/gitea-actions repo on Gitea. This repo is PUBLIC (required for runner auth to work with REQUIRE_SIGNIN_VIEW=false).

Available actions:

• cal/gitea-actions/calver@main — generates CalVer version (YYYY.MM.BUILD) from git tags
• cal/gitea-actions/gitea-tag@main — creates git tag via Gitea API
• cal/gitea-actions/discord-notify@main — sends Discord embed notification via webhook

Workflow reference patterns:

• Local actions (cal/gitea-actions): use SHORT FORM — uses: cal/gitea-actions/calver@main
• GitHub actions (actions/checkout etc): use FULL URL — uses: https://github.com/actions/checkout@v4

This is required because DEFAULT_ACTIONS_URL=self is set in Gitea app.ini, which resolves short-form references against the local Gitea instance.

When creating a new project workflow:

1. Copy an existing docker-build.yml or deploy.yml as template
2. Use short form for cal/gitea-actions/* references
3. Use https://github.com/ prefix for all GitHub action references
4. Secrets needed: DOCKERHUB_USERNAME, DOCKERHUB_TOKEN, DISCORD_WEBHOOK (for Docker builds)

Repos using this pattern: major-domo-database, paper-dynasty-discord, paper-dynasty-database, major-domo-v2, vagabond-rpg-foundryvtt