Skip to content

fleet status: run on the fleet-status read row, off the exec cap - #336

Merged
askalf merged 3 commits into
masterfrom
ci/fleet-status-read-row
Nov 1, 2026
Merged

askalf merged 3 commits into
masterfrom
ci/fleet-status-read-row

Conversation

@askalf

@askalf askalf commented Nov 1, 2026

Copy link
Copy Markdown
Owner

The fleet status job checks out nothing and only calls the API, but on this repository's exec runner each run held an exec cap slot that a test job had to wait for. It now runs on this repository's fleet status row (label fleet-status), a read-tier runner outside the exec cap. Fork behaviour is unchanged: there it still runs on GitHub's runners.

The fleet-status-check pin moves to askalf/ci@8b4fc27 (askalf/ci#156), which accepts fleet-status on the status workflows only.

.github/actionlint.yaml also lists the fleet-status label, so actionlint knows the runner.

@askalf
askalf enabled auto-merge (squash) November 1, 2026 23:35
@github-actions github-actions Bot added github_actions Pull requests that update GitHub Actions code size/S 10-49 hand-written lines labels Nov 1, 2026

@sprayberry-redline sprayberry-redline left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: approve. The runner expression selects fleet-status only for askalf/truecopy and preserves ubuntu-latest for forks. The matching actionlint label and pinned self-test update are consistent with that routing change; the status job retains its existing event guards and permissions.

@askalf
askalf merged commit 7cd9432 into master Nov 1, 2026
20 checks passed
@askalf
askalf deleted the ci/fleet-status-read-row branch November 1, 2026 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github_actions Pull requests that update GitHub Actions code size/S 10-49 hand-written lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants