Skip to content
Latchkey

Tests workflow (nolanlawson/fuite)

The Tests workflow from nolanlawson/fuite, explained and optimized by Latchkey.

F

CI health: F - at risk

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: nolanlawson/fuite.github/workflows/tests.ymlLicense Apache-2.0View source

What it does

This is the Tests workflow from the nolanlawson/fuite repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Tests
on:
  pull_request:
    branches: [ master ]
  push:
    branches: [ master ]
jobs:
  build:
    # Hopefully temporary fix for Puppeteer "No usable sandbox!" error which we get on Ubuntu 24.04+
    runs-on: ubuntu-22.04
    strategy:
      matrix:
        # The lowest one should be the minimum supported node version, per package.json "engines" field
        node: [ "18.0.0", "20", "22" ]
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - uses: pnpm/action-setup@v4
        with:
          node-version: ${{ matrix.node }}
          cache: 'pnpm'
      - run: pnpm install --frozen-lockfile
      - run: pnpm lint
      - run: pnpm test

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Tests
on:
  pull_request:
    branches: [ master ]
  push:
    branches: [ master ]
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    # Hopefully temporary fix for Puppeteer "No usable sandbox!" error which we get on Ubuntu 24.04+
    runs-on: latchkey-small
    strategy:
      matrix:
        # The lowest one should be the minimum supported node version, per package.json "engines" field
        node: [ "18.0.0", "20", "22" ]
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          cache: 'npm'
      - uses: pnpm/action-setup@v4
        with:
          node-version: ${{ matrix.node }}
          cache: 'pnpm'
      - run: pnpm install --frozen-lockfile
      - run: pnpm lint
      - run: pnpm test
 

What changed

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:

This workflow runs 1 job (3 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow