Repository navigation
fleet status: run on the fleet-status read row, off the exec cap - #271
Merged
Merged
Conversation
askalf
enabled auto-merge (squash)
November 1, 2026 23:20
github-actions
Bot
added
github_actions
sprayberry-redline
approved these changes
Nov 1, 2026
sprayberry-redline
left a comment
sprayberry-redline
left a comment
Collaborator
There was a problem hiding this comment.
Verdict: approve. The runner selection sends this repository's status job to the fleet-status label while preserving the hosted-runner fallback for forks and the existing event and permission boundaries. The companion workflow updates its validator to a full commit pin for the new runner label.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-checkpin moves to askalf/ci@8b4fc27 (askalf/ci#156), which acceptsfleet-statuson the status workflows only.