This PR standardizes the Gitea Actions workflows for web/phpapache to match the proven htpasswd pattern.
Changes:
main.yaml (push to master):
BREAKING: Remove the build-push job that pushed :latest to Docker Hub on every master push
Add test job as a mandatory step before build and tag
Add build job that just builds the image locally (no push)
tag job now depends on build passing
Switch from GITHUB_TOKEN to org-level SA_TOKEN_ACTION_PUSH_TAGS secret
Git URL: scm.cabillot.eu/web/phpapache.git
cron.yaml (nightly rebuild):
Add mandatory test job before build-push
build-push now needs: [test]
Remove the unconditional :latest tag push; only push {latest-tag}-latest
Cron schedule preserved: '0 0 * * *'
tag.yaml (tag release):
Add mandatory test job before build-push
build-push now needs: [test]
Add type=ref,event=tag,suffix=-latest meta tag alongside the plain tag reference
Rationale:
Tests are now mandatory before any image is built or pushed
No more :latest push on every master commit — that created unnecessary churn without a tag
Tag releases now push both {tag} and {tag}-latest for clear versioned images
## Standardize CI workflows
This PR standardizes the Gitea Actions workflows for `web/phpapache` to match the proven htpasswd pattern.
### Changes:
**main.yaml** (push to master):
- **BREAKING**: Remove the `build-push` job that pushed `:latest` to Docker Hub on every master push
- Add `test` job as a mandatory step before build and tag
- Add `build` job that just builds the image locally (no push)
- `tag` job now depends on `build` passing
- Switch from `GITHUB_TOKEN` to org-level `SA_TOKEN_ACTION_PUSH_TAGS` secret
- Git URL: `scm.cabillot.eu/web/phpapache.git`
**cron.yaml** (nightly rebuild):
- **Add mandatory `test` job** before `build-push`
- `build-push` now `needs: [test]`
- Remove the unconditional `:latest` tag push; only push `{latest-tag}-latest`
- Cron schedule preserved: `'0 0 * * *'`
**tag.yaml** (tag release):
- **Add mandatory `test` job** before `build-push`
- `build-push` now `needs: [test]`
- Add `type=ref,event=tag,suffix=-latest` meta tag alongside the plain tag reference
### Rationale:
- Tests are now mandatory before any image is built or pushed
- No more `:latest` push on every master commit — that created unnecessary churn without a tag
- Tag releases now push both `{tag}` and `{tag}-latest` for clear versioned images
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Standardize CI workflows
This PR standardizes the Gitea Actions workflows for
web/phpapacheto match the proven htpasswd pattern.Changes:
main.yaml (push to master):
build-pushjob that pushed:latestto Docker Hub on every master pushtestjob as a mandatory step before build and tagbuildjob that just builds the image locally (no push)tagjob now depends onbuildpassingGITHUB_TOKENto org-levelSA_TOKEN_ACTION_PUSH_TAGSsecretscm.cabillot.eu/web/phpapache.gitcron.yaml (nightly rebuild):
testjob beforebuild-pushbuild-pushnowneeds: [test]:latesttag push; only push{latest-tag}-latest'0 0 * * *'tag.yaml (tag release):
testjob beforebuild-pushbuild-pushnowneeds: [test]type=ref,event=tag,suffix=-latestmeta tag alongside the plain tag referenceRationale:
:latestpush on every master commit — that created unnecessary churn without a tag{tag}and{tag}-latestfor clear versioned images