CI workflow (outsourc-e/hermes-workspace)
The CI workflow from outsourc-e/hermes-workspace, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the CI workflow from the outsourc-e/hermes-workspace repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
# Phase 2.5-002: Build + lint workflow
# Runs on all PRs and pushes to main
name: CI
on:
push:
branches: [main, production]
pull_request:
branches: [main, production]
jobs:
build:
name: Build & Lint
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Setup pnpm
uses: pnpm/action-setup@v4
with:
version: 10
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'pnpm'
- name: Install dependencies
run: pnpm install --no-frozen-lockfile
- name: Run linter
run: pnpm run lint || echo "⚠️ Lint not configured, skipping"
continue-on-error: true
- name: Type check
run: pnpm run typecheck || pnpm exec tsc --noEmit || echo "⚠️ Typecheck not configured"
continue-on-error: true
- name: Build
run: pnpm build
- name: Verify build output
run: |
if [ -d "dist" ]; then
echo "✅ Build output exists"
ls -la dist/
else
echo "❌ No dist folder found"
exit 1
fi
test:
name: Run Tests
runs-on: ubuntu-latest
needs: build
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Setup pnpm
uses: pnpm/action-setup@v4
with:
version: 10
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '22'
cache: 'pnpm'
- name: Install dependencies
run: pnpm install --no-frozen-lockfile
- name: Run tests
run: pnpm test || echo "⚠️ No tests configured"
continue-on-error: true
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
# Phase 2.5-002: Build + lint workflow # Runs on all PRs and pushes to main name: CI on: push: branches: [main, production] pull_request: branches: [main, production] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 name: Build & Lint runs-on: latchkey-small steps: - name: Checkout code uses: actions/checkout@v4 - name: Setup pnpm uses: pnpm/action-setup@v4 with: version: 10 - name: Setup Node.js uses: actions/setup-node@v4 with: node-version: '22' cache: 'pnpm' - name: Install dependencies run: pnpm install --no-frozen-lockfile - name: Run linter run: pnpm run lint || echo "⚠️ Lint not configured, skipping" continue-on-error: true - name: Type check run: pnpm run typecheck || pnpm exec tsc --noEmit || echo "⚠️ Typecheck not configured" continue-on-error: true - name: Build run: pnpm build - name: Verify build output run: | if [ -d "dist" ]; then echo "✅ Build output exists" ls -la dist/ else echo "❌ No dist folder found" exit 1 fi test: timeout-minutes: 30 name: Run Tests runs-on: latchkey-small needs: build steps: - name: Checkout code uses: actions/checkout@v4 - name: Setup pnpm uses: pnpm/action-setup@v4 with: version: 10 - name: Setup Node.js uses: actions/setup-node@v4 with: node-version: '22' cache: 'pnpm' - name: Install dependencies run: pnpm install --no-frozen-lockfile - name: Run tests run: pnpm test || echo "⚠️ No tests configured" continue-on-error: true
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Cancel superseded runs when a branch or PR gets a newer push.
- Add a job timeout so a hung step cannot burn hours of runner time.
1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
What Latchkey heals here
This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:
- Dependency installs
This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.