CI never actually runs on this repo: GitHub-hosted runner labels don't exist on this Forgejo instance #19

New issue

Open

opened 2026-07-11 07:53:44 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-11 07:53:44 -07:00

Collaborator

What's happening

Every job on every push/PR (including PR #18) shows as Has been cancelled rather than a real pass or fail - e.g. the checks on PR #18's head commit (c357b7d) are all Has been cancelled across test (ubuntu-latest), test (windows-latest), test (macos-latest), and the package matrix jobs.

Root cause

.github/workflows/ci.yml requests runs-on: ubuntu-latest / windows-latest / macos-latest - these are GitHub-hosted runner labels. This repo lives on a self-hosted Forgejo instance (git.opensourcesolarpunk.com), which does not have macOS/Windows runners, and its ubuntu-latest-labeled runner(s) appear to be scoped to the Circuit-Forge org rather than available to personal-account repos - other repos on this same instance (circuitforge-core, peregrine, kiwi) all use .forgejo/workflows/ci.yml with runs-on: ubuntu-latest only, and those run successfully.

Suggested fix

Move (or add) the workflow to .forgejo/workflows/ci.yml (Forgejo-native path).
Drop the windows-latest/macos-latest matrix entries from the test job; keep ubuntu-latest only.
Confirm with the instance admin whether personal-account repos can get runner access, or whether this repo needs to move under an org that already has it.
Separately: the current test job only runs dart run scripts/test.dart (the pure-Dart workspace packages) - it never runs flutter analyze/flutter test/dart format for apps/focus_flow_flutter. Worth adding once CI is actually executing.

As a starting point, the Circuit-Forge/focus-flow fork now has a working .forgejo/workflows/ci.yml (ubuntu-latest only, covers both the workspace packages and the Flutter app) that could be ported back here directly.

## What's happening Every job on every push/PR (including PR #18) shows as `Has been cancelled` rather than a real pass or fail - e.g. the checks on PR #18's head commit (`c357b7d`) are all `Has been cancelled` across `test (ubuntu-latest)`, `test (windows-latest)`, `test (macos-latest)`, and the `package` matrix jobs. ## Root cause `.github/workflows/ci.yml` requests `runs-on: ubuntu-latest / windows-latest / macos-latest` - these are GitHub-hosted runner labels. This repo lives on a self-hosted Forgejo instance (`git.opensourcesolarpunk.com`), which does not have macOS/Windows runners, and its `ubuntu-latest`-labeled runner(s) appear to be scoped to the `Circuit-Forge` org rather than available to personal-account repos - other repos on this same instance (`circuitforge-core`, `peregrine`, `kiwi`) all use `.forgejo/workflows/ci.yml` with `runs-on: ubuntu-latest` only, and those run successfully. ## Suggested fix - Move (or add) the workflow to `.forgejo/workflows/ci.yml` (Forgejo-native path). - Drop the `windows-latest`/`macos-latest` matrix entries from the `test` job; keep `ubuntu-latest` only. - Confirm with the instance admin whether personal-account repos can get runner access, or whether this repo needs to move under an org that already has it. - Separately: the current `test` job only runs `dart run scripts/test.dart` (the pure-Dart workspace packages) - it never runs `flutter analyze`/`flutter test`/`dart format` for `apps/focus_flow_flutter`. Worth adding once CI is actually executing. As a starting point, the `Circuit-Forge/focus-flow` fork now has a working `.forgejo/workflows/ci.yml` (ubuntu-latest only, covers both the workspace packages and the Flutter app) that could be ported back here directly.