OSS-Singularity/zcode-dispatch-observatory
OSS-Singularity/zcode-dispatch-observatory
Watch
1
0
Fork
You've already forked zcode-dispatch-observatory
 0
Code Issues Pull requests Projects Releases 137 Packages Wiki Activity Actions

ci: forge-side check workflow on oss-oo-public (stops ubuntu-latest zombie runs) #21

Merged
ClaudiuSchuster merged 1 commit from oss-oo/forge-check-workflow into main 2026-09-24 14:46:52 +00:00
Conversation 0 Commits 1 Files changed 1 +41
ClaudiuSchuster commented 2026-09-24 14:44:25 +00:00
Owner

Cause

.github/workflows/check.yml requests runs-on: ubuntu-latest, but no forge runner serves that label (active fleet: oss-oo-public, oss-oo-internal). Every push and PR therefore created runs that waited forever — 22 such zombie runs accumulated since 2026-09-23 and were cancelled via the admin API on 2026-09-24.

Fix

Add a same-named .forgejo/workflows/check.yml. Forgejo shadows the .github copy per basename (same pattern as OSS-Singularity/website's static-publication.yml), so the forge lane stops requesting ubuntu-latest and gates on the functional checks (oss-oo-public, house-style manual checkout, no marketplace actions).

GitHub keeps running the unchanged .github/workflows/check.yml: Super-Linter and the social-preview byte-check are anchored to the GitHub runner toolchain (exact renderer versions) and are deliberately not ported.

## Cause `.github/workflows/check.yml` requests `runs-on: ubuntu-latest`, but no forge runner serves that label (active fleet: `oss-oo-public`, `oss-oo-internal`). Every push and PR therefore created runs that waited forever — 22 such zombie runs accumulated since 2026-09-23 and were cancelled via the admin API on 2026-09-24. ## Fix Add a same-named `.forgejo/workflows/check.yml`. Forgejo shadows the `.github` copy per basename (same pattern as OSS-Singularity/website's static-publication.yml), so the forge lane stops requesting `ubuntu-latest` and gates on the functional checks (`oss-oo-public`, house-style manual checkout, no marketplace actions). GitHub keeps running the unchanged `.github/workflows/check.yml`: Super-Linter and the social-preview byte-check are anchored to the GitHub runner toolchain (exact renderer versions) and are deliberately not ported.
ci: add forge-side check workflow on oss-oo-public
All checks were successful
Checks / Functional checks (pull_request) Successful in 14s
Details Explain this check
e831e45f7e 
The .github/workflows/check.yml requests ubuntu-latest, a label no
forge runner serves — every push/PR run waited forever (22 zombie
runs cancelled on 2026-09-24). A same-named .forgejo/workflows/
check.yml shadows it on the forge only; GitHub keeps the full suite
(Super-Linter + social-preview byte-check stay GitHub-anchored).
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
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
OSS-Singularity/zcode-dispatch-observatory!21
No description provided.