Skip to content

.github/workflows: Migrate workflows to Blacksmith runners - #16

Merged
ironystock merged 2 commits into
mainfrom
blacksmith-migration-708c2f3
Apr 28, 2026
Merged

ironystock merged 2 commits into
mainfrom
blacksmith-migration-708c2f3

Conversation

@blacksmith-sh

@blacksmith-sh blacksmith-sh Bot commented Apr 28, 2026 •

Copy link
Copy Markdown

To whomever may be reviewing this PR,

Blacksmith is the fastest way to run your GitHub Actions.

What does this PR change?

This PR has been automatically generated by a team member in your GitHub organization using Blacksmith's Migration Wizard, or MigWiz for short. This PR changes the following:

  1. Your selected workflows will now run on Blacksmith's 2x faster hardware (e.g., runs-on: blacksmith-4vcpu-ubuntu-2204). Learn more about the different instances available to choose from.
  2. Your jobs running on Blacksmith will now have all official GitHub and popular third-party cache actions automatically interact with our 4x faster, colocated cache. Learn more about Blacksmith's actions cache.
  3. Your GitHub Actions will now actually be observable. Learn more about Blacksmith's logging and other observability features.
  4. Your Docker builds will now automatically share their Docker layer cache, resulting in up to 40x faster builds. Learn more about Blacksmith's Docker layer caching.

FAQ

  • Is this free? The first 3,000 minutes per month are free.
  • Who uses Blacksmith? Clerk, Ashby, VEED, and 600+ others.
  • What's the catch? There is none. Merge this thing already.

View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

blacksmith-sh Bot and others added 2 commits April 28, 2026 14:41
Two issues caught by CI on the Blacksmith migration PR:

1) Mod tidy drift. PR #10 (logger + fang) shipped go.mod with
   charmbracelet/fang as `// indirect` even though main.go imports
   it directly, plus go.sum carried orphan entries from the
   cellbuf@latest upgrade (old ansi/cellbuf/term/displaywidth/uax29
   versions, two old colorprofile versions). `go mod tidy` cleans
   both up. The new mod-tidy CI check did exactly what it was added
   to do — caught the leftover hygiene before it could mask a real
   dep issue down the line.

2) Check-name drift from the Blacksmith migration. The wizard
   rewrote `windows-latest` -> `blacksmith-4vcpu-windows-2025` in
   matrix.os, which propagates into the job name `Test (...)` and
   therefore the GitHub check-run name. Main's branch protection
   ruleset requires the literal name `Test (windows-latest)` — so
   if this PR merged as-was, every future PR would be silently
   blocked by a required check that no workflow run ever produces.

   Fix: split matrix.os (stable label that drives the job name and
   ruleset matching) from matrix.runner (the actual runs-on value
   that can change). Same trick lets matrix Linux finally benefit
   from Blacksmith too — the wizard left it on GitHub-hosted ubuntu
   while moving the standalone jobs (mod-tidy, lint, goreleaser)
   to Blacksmith.

After this commit:
- Job names stay `Test (ubuntu-latest)` / `Test (macos-latest)` /
  `Test (windows-latest)` regardless of runner provider.
- Linux matrix runs on Blacksmith.
- macOS stays on GitHub-hosted (Blacksmith doesn't offer macOS).
- Windows runs on Blacksmith.
- Ruleset needs no change.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@ironystock
ironystock merged commit 87b4f88 into main Apr 28, 2026
7 checks passed
@ironystock
ironystock deleted the blacksmith-migration-708c2f3 branch April 28, 2026 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant