ci: run on GitHub-hosted runners instead of Blacksmith#33
Merged
Conversation
Ecko95/gitscode is not connected to Blacksmith, so every job requesting a
`blacksmith-*` runner label sat queued forever (no runner registered under this
account) — blocking all PR checks. Blacksmith itself is healthy; the labels were
inherited from upstream t3code, which has its own Blacksmith org.
Swap to GitHub-hosted runners (label-only change — the workflows already use
standard actions/cache, setup-bun, setup-node, with no useblacksmith/* steps):
- blacksmith-{8,32}vcpu-ubuntu-2404 → ubuntu-24.04
- blacksmith-12vcpu-macos-26 → macos-15
- blacksmith-32vcpu-windows-2025 → windows-2025
Trade-off: GitHub-hosted runners are slower and bill Actions minutes. Re-point
to blacksmith-* once the account is connected at app.blacksmith.sh.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
`bun run fmt:check` (oxfmt --check, repo-wide) flagged 27 files that drifted out of format while CI was unable to run (the Blacksmith runner stall meant the Format gate never executed on these merges). Applying `oxfmt` — whitespace/style only, no semantic changes — so the now-working Format gate passes. None of these are visual-plan Phase 2 files; all are pre-existing gits content (docs, plans, and a handful of TS/TSX from earlier merges). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Three deterministic, safe fixes for pre-existing test debt that only surfaced now that CI runs (the Blacksmith stall meant these gates never executed): - apps/mobile threadActivity: add `visualPlans: []` to the OrchestrationThread fixture — the field became required when visual-plan landed (Phase 1). - apps/server projector.test: add `visualPlans: []` to the expected projected thread for `thread.created` — same reason. - scripts build-desktop-artifact: the alpha product name is "GITS (Alpha)" after the rebrand (resolveDesktopProductName reads the desktop package.json); update the stale "T3 Code (Alpha)" assertion to match actual behaviour. The remaining pre-existing failures (desktop app-identity migration, codex adapter, provider-registry clock, oxlint-plugin rule, effect-acp, web MessagesTimeline) need per-domain investigation and are tracked separately. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Ecko95
added a commit
that referenced
this pull request
Jun 21, 2026
…swap) PR #33 moved ci.yml off Blacksmith onto slower GitHub-hosted ubuntu-24.04 runners; format+lint+typecheck+test now reach ~10m, so the job was canceled at "Install browser test runtime" on every PR. Raising timeout-minutes to fit the full pipeline (browser test + desktop build). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Why CI was stuck
Ecko95/gitscodeis not connected to Blacksmith, so every job requesting ablacksmith-*runner label (Format/Lint/Typecheck/Test/Build, Mobile Native, Release Smoke) sat queued forever — no runner is registered under this account (confirmed: Settings → Actions → Runners is empty). The lightweight jobs useubuntu-24.04GitHub-hosted runners, which is why only those ever passed.Blacksmith itself is fully operational — the
blacksmith-*labels were inherited from upstreamt3code, which has its own Blacksmith org. This blocked PR checks on #30 / #31 / #32 (all merged after local verification + admin override).Change
Label-only swap to GitHub-hosted runners. The workflows already use standard
actions/cache@v5,oven-sh/setup-bun,actions/setup-node— there are nouseblacksmith/*actions or sticky-disk steps to migrate.blacksmith-{8,32}vcpu-ubuntu-2404ubuntu-24.04blacksmith-12vcpu-macos-26macos-15blacksmith-32vcpu-windows-2025windows-2025Touches
ci.yml(3) andrelease.yml(10). Both files still parse; there's already precedent for this swap (the commentedubuntu-24.04 # blacksmith-...atrelease.yml).Trade-off / follow-up
GitHub-hosted runners are slower and bill Actions minutes (macOS = 10× multiplier). To restore the fast Blacksmith runners, connect the account at app.blacksmith.sh and re-point the labels.
This PR's own CI run will exercise the new runners — first real CI on
gitssince the Blacksmith stall.🤖 Generated with Claude Code