Repository navigation
feat(ci): choose hosted vs local runners for strict Rust by visibility - #173
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Apply the same repository-visibility runner policy as ci-workflows #50 to the reusable strict Rust gate.
ubuntu-24.04.['self-hosted','Linux','X64'], allowing any online registered local Acer/Asus runner instead of forcing the Asus label. No caller configuration or private hosted-runner bypass.3a19d861aced60226c05c499fecc6761b66a6f49. That provider selects the existing managed socket/client by local capabilities and does not create extra cache daemons.Focused tests:
uv run --no-project python checks/test_action_pins.py, YAML parsing, andgit diff --checkpass. Await exact-head CI checks before merge. Existing direct per-repo jobs with hardcodedasusremain separate; this change affects the shared strict-Rust gate, not every private YAML file.