CI workflow (realiti4/claude-swap)
The CI workflow from realiti4/claude-swap, 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 realiti4/claude-swap 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
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# uv (not pip) so the PEP 735 dev dependency-group - pytest,
# pytest-asyncio - installs from the committed lockfile, same as local
# development.
- name: Install uv
uses: astral-sh/setup-uv@v6
with:
python-version: '3.12'
- name: Install dependencies
run: uv sync
- name: Run tests
run: uv run pytest
test-windows:
runs-on: windows-latest
steps:
- uses: actions/checkout@v4
- name: Install uv
uses: astral-sh/setup-uv@v6
with:
python-version: '3.12'
- name: Install dependencies
run: uv sync
- name: Run tests
# Includes the TUI tests: the Textual TUI (unlike the old curses one)
# runs on stock Windows, and this job is the proof.
run: uv run pytest
macos-keychain:
runs-on: macos-latest
steps:
- uses: actions/checkout@v4
- name: Install uv
uses: astral-sh/setup-uv@v6
with:
python-version: '3.12'
- name: Install dependencies
run: uv sync
- name: Run macOS Keychain tests (contract + real security wrapper)
# faulthandler dumps every thread's stack if a test exceeds 60s - a
# `security` call blocking on an invisible SecurityAgent dialog would
# otherwise hang the job with no clue where. The step timeout is the
# backstop that actually kills it.
timeout-minutes: 5
run: uv run pytest tests/test_macos_keychain_contract.py tests/test_macos_keychain.py -v -o faulthandler_timeout=60
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: CI on: push: branches: [main] pull_request: branches: [main] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: test: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v4 # uv (not pip) so the PEP 735 dev dependency-group - pytest, # pytest-asyncio - installs from the committed lockfile, same as local # development. - name: Install uv uses: astral-sh/setup-uv@v6 with: python-version: '3.12' - name: Install dependencies run: uv sync - name: Run tests run: uv run pytest test-windows: timeout-minutes: 30 runs-on: windows-latest steps: - uses: actions/checkout@v4 - name: Install uv uses: astral-sh/setup-uv@v6 with: python-version: '3.12' - name: Install dependencies run: uv sync - name: Run tests # Includes the TUI tests: the Textual TUI (unlike the old curses one) # runs on stock Windows, and this job is the proof. run: uv run pytest macos-keychain: timeout-minutes: 30 runs-on: macos-latest steps: - uses: actions/checkout@v4 - name: Install uv uses: astral-sh/setup-uv@v6 with: python-version: '3.12' - name: Install dependencies run: uv sync - name: Run macOS Keychain tests (contract + real security wrapper) # faulthandler dumps every thread's stack if a test exceeds 60s - a # `security` call blocking on an invisible SecurityAgent dialog would # otherwise hang the job with no clue where. The step timeout is the # backstop that actually kills it. timeout-minutes: 5 run: uv run pytest tests/test_macos_keychain_contract.py tests/test_macos_keychain.py -v -o faulthandler_timeout=60
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.
This workflow runs 3 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.