feat(blacksmith): migrate a repo's GitHub Actions compute to Blacksmith runners - #53
Merged
Conversation
…th runners One FSH repo was moved to Blacksmith by hand and the rules that came out of it were worth keeping: move only what builds, runs or tests the app, at the same vCPU count; give image builds the sticky-disk Docker actions and drop the external layer cache (measured 12.4 → 3.6 min on one build, hardware −53% and the disk a further −33%); leave glue, deploy, self-hosted and credential-bound jobs where they are, because faster cores buy them nothing and the merge gate should sit on the most boring infrastructure available. The skill gates on the GitHub App being installed (without it blacksmith-* jobs queue forever), inventories every job with a suggested verdict it must still judge, captures a priced timing baseline before editing, and hands off to deliver --no-merge with the decision table in the PR. It refuses pilot scaffolding (runner inputs, label-guarded dual step paths) — the PR is the rollback unit — and treats a self-triggering workflow that has been dormant as something to expect a pre-existing failure from, not to fix. Bundled: inventory.sh (PyYAML, read-only, dormancy check via gh), ci-timing.sh (per-workflow wall-clock and cost at both vendors' rates), an actionlint.yaml template so the labels don't read as typos, and references/policy.md with the measurements the policy rests on. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.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
One FSH repo was moved to Blacksmith by hand. The rules that came out of it — which jobs to move, how to rewrite image builds for the sticky-disk cache, what to leave alone and why, how to measure without fooling yourself — lived in one PR thread. The next repos would re-derive them.
What this adds
/fsh:blacksmith— run inside any repo:blacksmith-*jobs queue until GitHub times them out).scripts/inventory.shprints one row per job with the classification signals and a suggested verdict;scripts/ci-timing.shprices the last 14 days per workflow and runner label.useblacksmith/*@v2, constantcache-key, dropcache-from/cache-to), unit/lint/typecheck, service-container tests, browser e2e, CPU-bound bundle steps.if: always()gates, notifiers, PR commenters, paths-filter, deploys and health checks that wait on a cluster, self-hosted jobs, machine-local or network-scoped credentials.actionlintwith the bundled config template,timeout-minuteson every migrated job, then/deliver --no-mergewith the decision table and baseline in the PR body.references/policy.mdcarries the measurements the policy rests on (hardware −53%, sticky disk a further −33% on one image build; n=1 misled twice).Verified
shellcheck+bash -nclean on both scripts.fsh-monorepo: 2 image builds + 3 test/build jobs → migrate; every deploy, reaper and notifier → stay; 3 callers resolved to their callees.main: every moved job reportsDONE, the required-check aggregator reportsSTAY, and a self-triggering workflow idle for 63 days is flagged as the one whose edit will wake a pre-existing failure.ci-timing.shagainstfsh-monorepo(5 runs/workflow) returns priced rows.plugin.json1.6.0 → 1.7.0 (new skill).🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.