CI: standardize workflows #7
Reference in New Issue
Block a user
Delete Branch "fix/workflow-standard"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Standardise CI/CD pipelines by adopting the canonical 4-workflow pattern (main.yaml, cron.yaml, tag.yaml, pr.yaml), matching the htpasswd convention exactly.
Changes
.gitea/workflows/docker-build.yaml— removed (replaced by the 4-file standard).gitea/workflows/main.yaml— push to master: lint, build, test, push to Docker Hub, auto-bump version.gitea/workflows/cron.yaml— nightly rebuild on schedule (0 0 * * *).gitea/workflows/tag.yaml— tag release (v*): build and push with semver tags via docker/metadata-action.gitea/workflows/pr.yaml— PR checks: hadolint + build smoke-testAction versions (pinned by SHA)
df4cb1c...#v62332a7b...#v3.3.0d7f5e7f...#v4650006c...#v480c7e94...#v6f9f3042...#v7.2.04ed4496...#v1.75.0