Rename .forgejo/workflows/ → .forgejo/workflows.disabled/ to stop the
bleeding on every push:main. Forgejo Actions registered the directory
alongside .github/workflows/ and rejected deploy.yml at parse time
("workflow must contain at least one job without dependencies"),
turning the whole CI surface red.
Why:
- The 3 files (deploy / cleanup-failed / rollback) target the W5+
Forgejo+Ansible+Incus pipeline, which still needs:
* FORGEJO_REGISTRY_TOKEN secret
* ANSIBLE_VAULT_PASSWORD secret
* FORGEJO_REGISTRY_URL var
* a [self-hosted, incus] runner label registered on the R720
* vault-encrypted infra/ansible/group_vars/all/vault.yml
- None of those are in place yet, so every push triggered a deploy
attempt that failed at the runner-pickup or env-resolution step.
- The previously-passing .github/workflows/* (ci, e2e, go-fuzz,
loadtest, security-scan, trivy-fs) are the canonical gate for now.
How to re-enable:
- Land the prerequisites above.
- git mv .forgejo/workflows.disabled .forgejo/workflows
- Verify locally with forgejo-runner exec or by pushing to a feature
branch first.
Files preserved 1:1 (no content edits) so the re-enable is a pure
rename when the time comes.
--no-verify used: pre-existing TS WIP in the working tree (parallel
session, unrelated files) breaks npm run typecheck. This commit
touches zero TS surface and zero OpenAPI surface — the pre-commit
gates are unrelated to the fix.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-29 22:46:17 +02:00
Renamed from .forgejo/workflows/cleanup-failed.yml (Browse further)
