Test commit workflow (john-hen/Flake8-pyproject)

The Test commit workflow from john-hen/Flake8-pyproject, explained and optimized by Latchkey.

What it does

This is the Test commit workflow from the john-hen/Flake8-pyproject 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

# Test commit on all supported platforms and Python versions.

name: Test commit


on: [push, pull_request, workflow_dispatch]


jobs:

  # Test on all three platforms.

  platform:

    strategy:
      matrix:
        os: [windows-latest, ubuntu-latest, macos-latest]


    runs-on: ${{ matrix.os }}


    steps:
      - name: Check out code.

        uses: actions/checkout@v7


      - name: Set up Python.

        uses: actions/setup-python@v6

        with:
            python-version: 3.x


      - name: Install project.

        run:  pip install .[dev]


      - name: Run tests.

        run:  pytest



  # Test on all supported Python versions.

  Python:

    strategy:
        matrix:
            python: ['3.10', '3.11', '3.12', '3.13', '3.14']


    runs-on: ubuntu-latest


    steps:
      - name: Check out code.

        uses: actions/checkout@v7


      - name: Set up Python ${{ matrix.python }}.

        uses: actions/setup-python@v6

        with:
            python-version: ${{ matrix.python }}

            allow-prereleases: true


      - name: Install package.

        run:  pip install .[dev]


      - name: Run tests.

        run:  pytest

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.

# Test commit on all supported platforms and Python versions.

name: Test commit



on: [push, pull_request, workflow_dispatch]



concurrency:

  group: ${{ github.workflow }}-${{ github.ref }}

  cancel-in-progress: true



jobs:



  # Test on all three platforms.

  platform:



    strategy:

      matrix:

        os: [windows-latest, ubuntu-latest, macos-latest]



    runs-on: ${{ matrix.os }}



    steps:

      - name: Check out code.

        uses: actions/checkout@v7



      - name: Set up Python.

        uses: actions/setup-python@v6

        with:

          cache: 'pip'

            python-version: 3.x



      - name: Install project.

        run:  pip install .[dev]



      - name: Run tests.

        run:  pytest





  # Test on all supported Python versions.

  Python:



    strategy:

        matrix:

            python: ['3.10', '3.11', '3.12', '3.13', '3.14']



    runs-on: latchkey-small



    steps:

      - name: Check out code.

        uses: actions/checkout@v7



      - name: Set up Python ${{ matrix.python }}.

        uses: actions/setup-python@v6

        with:

          cache: 'pip'

            python-version: ${{ matrix.python }}

            allow-prereleases: true



      - name: Install package.

        run:  pip install .[dev]



      - name: Run tests.

        run:  pytest



 

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.

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 (8 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