Direct push to main: 6355e64 #1

Closed
opened 2026-10-24 10:36:19 +00:00 by gitea-actions · 1 comment

Direct push to main detected - commit was not associated with a merged PR.

The project policy is that all changes to main go through a pull request so they can be reviewed before deploying to production. If this push was intentional (hotfix, infra change) close this issue with a comment explaining why.

Opened automatically by the audit-direct-push action (peptide-e2e).

**Direct push to `main` detected** - commit was not associated with a merged PR. - Commit: `6355e64` - ci(gitea): longer MySQL service health window for wp-framework tests - Pusher: @admin - Workflow run: https://git.protopeer.com/peptide-repo/peptide-starter-theme/actions/runs/2 The project policy is that all changes to `main` go through a pull request so they can be reviewed before deploying to production. If this push was intentional (hotfix, infra change) close this issue with a comment explaining why. _Opened automatically by the audit-direct-push action (peptide-e2e)._
gitea-actions bot added the policy-violationaudit labels 2026-10-24 10:36:19 +00:00
Owner

Expected: Gitea Actions migration commit (6355e64) pushed directly while fixing the pipeline's MySQL service (2026-10-24). Closing.

Expected: Gitea Actions migration commit (6355e64) pushed directly while fixing the pipeline's MySQL service (2026-10-24). Closing.
admin closed this issue 2026-10-24 11:02:41 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: peptide-repo/peptide-starter-theme#1