Skip to content
Latchkey

Test suite workflow (kislyuk/yq)

The Test suite workflow from kislyuk/yq, 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: kislyuk/yq.github/workflows/ci.ymlLicense Apache-2.0View source

What it does

This is the Test suite workflow from the kislyuk/yq 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: Test suite

on: [push, pull_request]

jobs:
  unit_tests:
    runs-on: ${{matrix.os}}
    strategy:
      max-parallel: 8
      matrix:
        os: [ubuntu-22.04, ubuntu-latest, macos-15, macos-latest]
        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
    steps:
    - uses: actions/checkout@v7
    - uses: actions/setup-python@v6
      with:
        python-version: ${{matrix.python-version}}
        allow-prereleases: true
    - name: Install jq
      run: |
        if [[ $(uname) == Linux ]]; then sudo apt-get install --yes jq; fi
        if [[ $(uname) == Darwin ]]; then brew install jq; fi
    - run: make install
    - if: ${{matrix.python-version == '3.14'}}
      run: make lint
    - run: make test
    - uses: codecov/codecov-action@v5
  ruff:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: astral-sh/ruff-action@v4.0.0
      - uses: astral-sh/ruff-action@v4.0.0
        with:
          args: "format --check"

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: Test suite
 
on: [push, pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  unit_tests:
    timeout-minutes: 30
    runs-on: ${{matrix.os}}
    strategy:
      max-parallel: 8
      matrix:
        os: [ubuntu-22.04, ubuntu-latest, macos-15, macos-latest]
        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
    steps:
    - uses: actions/checkout@v7
    - uses: actions/setup-python@v6
      with:
        cache: 'pip'
        python-version: ${{matrix.python-version}}
        allow-prereleases: true
    - name: Install jq
      run: |
        if [[ $(uname) == Linux ]]; then sudo apt-get install --yes jq; fi
        if [[ $(uname) == Darwin ]]; then brew install jq; fi
    - run: make install
    - if: ${{matrix.python-version == '3.14'}}
      run: make lint
    - run: make test
    - uses: codecov/codecov-action@v5
  ruff:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
      - uses: astral-sh/ruff-action@v4.0.0
      - uses: astral-sh/ruff-action@v4.0.0
        with:
          args: "format --check"
 

What changed

2 third-party actions are referenced by a movable tag. Pin them 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 2 jobs (25 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