Lint workflow (opencontainers/runtime-spec)

The Lint workflow from opencontainers/runtime-spec, explained and optimized by Latchkey.

What it does

This is the Lint workflow from the opencontainers/runtime-spec 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

name: Lint

on: [push, pull_request]

jobs:
  check-format:
    runs-on: ubuntu-24.04
    steps:
    - name: Checkout code
      uses: actions/checkout@v4
    - name: Run make -C schema fmt
      run: make -C schema fmt
    - name: Check for changes
      run: git diff --exit-code

  codespell:
    runs-on: ubuntu-24.04
    steps:
    - uses: actions/checkout@v4
    - name: install deps
      run: pip install --break-system-packages codespell==v2.4.1
    - name: run codespell
      run: codespell

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Lint
 
on: [push, pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  check-format:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - name: Checkout code
      uses: actions/checkout@v4
    - name: Run make -C schema fmt
      run: make -C schema fmt
    - name: Check for changes
      run: git diff --exit-code
 
  codespell:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - uses: actions/checkout@v4
    - name: install deps
      run: pip install --break-system-packages codespell==v2.4.1
    - name: run codespell
      run: codespell
 

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 uses latchkey-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.

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.

Actions used in this workflow