Build workflow (PyCQA/autoflake)

The Build workflow from PyCQA/autoflake, explained and optimized by Latchkey.

What it does

This is the Build workflow from the PyCQA/autoflake 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: Build
on:
  push:
    branches:
      - main

  pull_request:
    branches:
      - main

jobs:
  test:
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
        os:
          - macos
          - ubuntu
          - windows

    name: tests
    runs-on: ${{ matrix.os }}-latest
    steps:
      - uses: actions/checkout@v6.0.2

      - uses: actions/setup-python@v6.2.0
        with:
          python-version: ${{ matrix.python-version }}

      - run: pip install .

      - run: pip install pytest

      - name: run tests
        run: pytest

  lint:
    name: pre-commit
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6.0.2

      - uses: actions/setup-python@v6.2.0
        with:
          python-version: 3.x

      - name: install package
        run: pip install . tomli

      - name: run pre-commit
        uses: pre-commit/action@v3.0.1

  fuzz:
    name: fuzz
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6.0.2

      - uses: actions/setup-python@v6.2.0
        with:
          python-version: 3.x

      - run: pip install .

      - name: run fuzz
        run: python test_fuzz.py ./*.py

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: Build
on:
  push:
    branches:
      - main
 
  pull_request:
    branches:
      - main
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  test:
    timeout-minutes: 30
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
        os:
          - macos
          - ubuntu
          - windows
 
    name: tests
    runs-on: ${{ matrix.os }}-latest
    steps:
      - uses: actions/checkout@v6.0.2
 
      - uses: actions/setup-python@v6.2.0
        with:
          cache: 'pip'
          python-version: ${{ matrix.python-version }}
 
      - run: pip install .
 
      - run: pip install pytest
 
      - name: run tests
        run: pytest
 
  lint:
    timeout-minutes: 30
    name: pre-commit
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v6.0.2
 
      - uses: actions/setup-python@v6.2.0
        with:
          cache: 'pip'
          python-version: 3.x
 
      - name: install package
        run: pip install . tomli
 
      - name: run pre-commit
        uses: pre-commit/action@v3.0.1
 
  fuzz:
    timeout-minutes: 30
    name: fuzz
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v6.0.2
 
      - uses: actions/setup-python@v6.2.0
        with:
          cache: 'pip'
          python-version: 3.x
 
      - run: pip install .
 
      - name: run fuzz
        run: python test_fuzz.py ./*.py
 

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.
• Cache dependency installs on the setup step so they are served from cache.
• 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 3 jobs (17 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