docs: clarify runner ownership in the README intro - #493
Merged
Merged
Conversation
…-hosted Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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.
Problem
The README intro states the generated workflows run on GitHub's own runners as a flat blanket. That reads as if the whole pipeline is locked to GitHub-hosted runners. It is not: cascade's own orchestration jobs run on
ubuntu-latest, but your build and deploy callbacks are your ownworkflow_callworkflows, and GitHub Actions determines their runner inside the callback (GitHub Actions forbidsruns-onon a job that calls a reusable workflow). So a consumer already controls hosted vs self-hosted for the actual work.Fix
Reword the intro to say everything runs as native GitHub Actions with no external control plane, and add that build and deploy callbacks run on whatever runners you configure, GitHub-hosted or self-hosted. The manifest reference already documents
runs_onas validated-only.Verification
Single-line prose change. README keeps its two schema-valid manifest examples; the docs build and the README-examples schema test are unaffected.