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

Forgejo Actions runner idle since 2026-05-31: no CI run for pushes to main #288

New issue
Closed
opened 2026-06-12 05:40:12 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-06-12 05:40:12 +00:00
Owner
Copy link

Pushing 46a3505 (merge of the GitHub mirror divergence) to canonical main on 2026-06-11 produced no Forgejo Actions run. The newest workflow runs on this repo are for 8eb4058 dated 2026-05-31, so the in-cluster forgejo-runner appears to have stopped picking up jobs roughly 11 days ago.

Observed via GET /api/v1/repos/coilyco-flight-deck/infrastructure/actions/tasks:

8eb4058 lint success created=2026-05-31T02:27:37Z branch=main
a09cb3f lint success created=2026-05-30T17:36:58Z branch=main

Next steps:

  • Check the forgejo-runner deployment on kai-server (deploy/forgejo-runner.yml, tap-writer runner workingDir trap in docs/k3s-deploy-notes.md).
  • Once the runner is back, confirm 46a3505 (or the then-current main tip) gets a lint + secret-scan run.

Context: the push itself landed clean on both Forgejo and the GitHub mirror, and the full local pre-commit suite (which mirrors the CI lint job) passed. This issue is only about the missing CI execution.

Pushing `46a3505` (merge of the GitHub mirror divergence) to canonical `main` on 2026-06-11 produced no Forgejo Actions run. The newest workflow runs on this repo are for `8eb4058` dated 2026-05-31, so the in-cluster forgejo-runner appears to have stopped picking up jobs roughly 11 days ago. Observed via `GET /api/v1/repos/coilyco-flight-deck/infrastructure/actions/tasks`: ``` 8eb4058 lint success created=2026-05-31T02:27:37Z branch=main a09cb3f lint success created=2026-05-30T17:36:58Z branch=main ``` Next steps: * Check the forgejo-runner deployment on kai-server (`deploy/forgejo-runner.yml`, tap-writer runner workingDir trap in docs/k3s-deploy-notes.md). * Once the runner is back, confirm `46a3505` (or the then-current `main` tip) gets a lint + secret-scan run. Context: the push itself landed clean on both Forgejo and the GitHub mirror, and the full local pre-commit suite (which mirrors the CI lint job) passed. This issue is only about the missing CI execution.
coilysiren 2026-06-17 07:06:09 +00:00
  • closed this issue
  • added the
    P0
         label
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#288
No description provided.