Prove Blacksmith runner availability#1
Merged
Conversation
Add a manual-only Blacksmith smoke workflow so KyaniteLabs can verify the org runner integration before migrating required CI jobs. Constraint: Blacksmith is organization-only, so this canary must run under KyaniteLabs rather than the personal namespace. Rejected: Convert production CI jobs immediately | Smoke must prove org runner availability before required checks depend on it. Confidence: high Scope-risk: narrow Directive: Keep this workflow manual-only until Blacksmith availability is proven. Tested: Local YAML file created and staged in isolated KyaniteLabs/Creator-kit clone. Not-tested: Blacksmith run pending remote workflow dispatch after push. Co-authored-by: OmX <omx@oh-my-codex.dev>
Allow the canary PR itself to prove Blacksmith runner availability, because GitHub cannot manually dispatch a workflow before the workflow exists on the default branch. Constraint: The workflow remains narrow and path-scoped to avoid spending Blacksmith minutes on unrelated PR updates. Rejected: Merge first then dispatch | That would prove the runner only after changing the default branch. Confidence: high Scope-risk: narrow Directive: Remove or keep this as manual-only after the Blacksmith integration is proven. Tested: Workflow syntax edited in isolated Creator-kit clone. Not-tested: Remote Blacksmith run pending after push. Co-authored-by: OmX <omx@oh-my-codex.dev>
The PR-triggered canary proved KyaniteLabs Blacksmith runner availability, so keep the default-branch smoke workflow manual-only to avoid spending free minutes on unrelated PRs. Constraint: Blacksmith free minutes should be reserved for high-signal checks. Rejected: Leave PR trigger enabled | It would run on every edit to the canary workflow after integration is already proven. Confidence: high Scope-risk: narrow Directive: Use this workflow as an explicit Blacksmith health probe, not as a required merge gate. Tested: Remote PR run 25191262401 passed on blacksmith-2vcpu Ubuntu runner. Not-tested: Manual dispatch from default branch until after merge. Co-authored-by: OmX <omx@oh-my-codex.dev>
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.
Summary\n- Adds a manual-only Blacksmith smoke workflow.\n- Uses
blacksmith-2vcpu-ubuntu-2404to verify KyaniteLabs org runner integration before any required CI jobs migrate.\n\n## Why\nBlacksmith is organization-only, so this canary must run under KyaniteLabs rather than a personal repo.\n\n## Verification\n- Local isolated clone commit created.\n- Remote workflow dispatch will be run after this PR exists.\n\nConstraint: Do not make Blacksmith a required check until this smoke workflow proves runner availability.\nNeed help on this PR? Tag
@codesmithwith what you need.