Repository navigation
Allow repositories to choose their CI runner - #17
Merged
Merged
Conversation
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
1 participant
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.
Fulldev is moving its CI jobs to Blacksmith, but the shared Check and Ready workflows currently hardcode GitHub-hosted runners.
Add an optional
runnerinput to both reusable workflows. It defaults toubuntu-latest, so existing pinned callers and callers that omit the input keep their current behavior. Permissions, checks, draft handling and merge policy stay unchanged.Validation: all 26 existing Ready policy tests pass with
vp node --test tests/ready.test.mjs;git diff --checkpasses. This is the prerequisite for the Fulldev monorepo pilot. Merge this first, then pin its merged main revision in the monorepo caller PR.