Repository navigation
fleet status: run on the fleet-status read row, off the exec cap - #197
Merged
Merged
Conversation
askalf
enabled auto-merge (squash)
November 1, 2026 22:35
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 routes this repository's status job to the fleet-status label while preserving the hosted-runner fallback for forks. The event guards, scoped permissions, and pinned action remain unchanged.
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.
This moves the
fleet-statusjob from this repository's exec row to its own read-tier fleet status row (labelfleet-status, added in pitlane-box#103; online since 2026-11-01 22:33Z). The job checks out nothing and runs only the pinned fleet-status action. On the exec row, each of these few-second runs held anEXEC_CAPslot, and in PR waves test jobs queued behind them. Read-tier rows are not counted by the cap. The trigger, concurrency and the action pin are unchanged. A fork repository still runs the job on GitHub's runners.