coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Forgejo Actions runner not triggering on recent main pushes #220

New issue
Open
opened 2026-06-04 10:10:08 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-06-04 10:10:08 +00:00
Owner
Copy link

Forgejo Actions has not run for the last several pushes to main. As of 2026-06-04 the newest task in coily ops forgejo actions task list --repo coilyco-flight-deck/infrastructure is run#137 (commit 8eb40580, "fix(coily-update): cap memory..."), but at least four later commits have landed with no lint / Scan-for-secrets run:

  • fb4c111 feat(ansible): declare scc + repomix in mac homebrew baseline
  • d8b368a fix(ansible): repair stale entries in mac homebrew baseline
  • 3a2b010 feat(ansible): enable code-comments on YAML, trim ansible, grandfather debt
  • 29537c0 feat(ansible): port up-to-date.py reconcile + deptree roles

.forgejo/workflows/{lint,trufflehog}.yml are 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-runner deploy). Surfaced from a session that validated its own changes locally (full pre-commit run --all-files green) since CI could not confirm.

Forgejo Actions has not run for the last several pushes to `main`. As of 2026-06-04 the newest task in `coily ops forgejo actions task list --repo coilyco-flight-deck/infrastructure` is run#137 (commit 8eb40580, "fix(coily-update): cap memory..."), but at least four later commits have landed with no lint / Scan-for-secrets run: - fb4c111 feat(ansible): declare scc + repomix in mac homebrew baseline - d8b368a fix(ansible): repair stale entries in mac homebrew baseline - 3a2b010 feat(ansible): enable code-comments on YAML, trim ansible, grandfather debt - 29537c0 feat(ansible): port up-to-date.py reconcile + deptree roles `.forgejo/workflows/{lint,trufflehog}.yml` are 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-runner` deploy). Surfaced from a session that validated its own changes locally (full `pre-commit run --all-files` green) since CI could not confirm.
coilysiren added
P3
 and removed
P2
 labels 2026-06-17 08:39:58 +00:00
coilyco-ops added
P2
 and removed
P3
 labels 2026-07-10 09:00:20 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#220
No description provided.