Forgejo Actions runner not triggering on recent main pushes #220
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#220
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Forgejo Actions has not run for the last several pushes to
main. As of 2026-06-04 the newest task incoily ops forgejo actions task list --repo coilyco-flight-deck/infrastructureis run#137 (commit8eb40580, "fix(coily-update): cap memory..."), but at least four later commits have landed with no lint / Scan-for-secrets run:fb4c111feat(ansible): declare scc + repomix in mac homebrew baselined8b368afix(ansible): repair stale entries in mac homebrew baseline3a2b010feat(ansible): enable code-comments on YAML, trim ansible, grandfather debt29537c0feat(ansible): port up-to-date.py reconcile + deptree roles.forgejo/workflows/{lint,trufflehog}.ymlare present and push-triggered, so this looks like the in-cluster runner stalling, not a content failure. Needs a runner health check on kai-server (forgejo-runnerdeploy). Surfaced from a session that validated its own changes locally (fullpre-commit run --all-filesgreen) since CI could not confirm.The agent is merging this duplicate June 4 runner-trigger incident into #214. Both issues describe the same missing push-triggered Actions runs, and #214 is the lower-numbered canonical record.