Skip to content
Latchkey

Continuous Integration workflow (pyparsing/pyparsing)

The Continuous Integration workflow from pyparsing/pyparsing, explained and optimized by Latchkey.

D

CI health: D - needs work

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: pyparsing/pyparsing.github/workflows/ci.ymlLicense MITView source

What it does

This is the Continuous Integration workflow from the pyparsing/pyparsing 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

workflow (.yml)
name: Continuous Integration
on:
  push:
    branches:
      - master

  pull_request:
    paths:
      - .github/workflows/ci.yml
      - pyparsing/*
      - pyproject.toml
      - tox.ini

permissions:
  contents: read

jobs:
  tests:
    name: Unit tests
    runs-on: ${{ matrix.os || 'ubuntu-latest' }}
    strategy:
      matrix:
        os: ["ubuntu-latest"]
        toxenv: [py]
        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]
        include:
          - python-version: "3.14"
            os: macos-latest
          - python-version: "3.12"
            toxenv: mypy-check
          - python-version: "pypy-3.9"
    env:
      TOXENV: ${{ matrix.toxenv || 'py' }}
    steps:
      - uses: actions/checkout@v5

      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v6
        with:
          python-version: ${{ matrix.python-version }}

      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install tox railroad-diagrams Jinja2

      - name: Test
        run: tox

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: Continuous Integration
on:
  push:
    branches:
      - master
 
  pull_request:
    paths:
      - .github/workflows/ci.yml
      - pyparsing/*
      - pyproject.toml
      - tox.ini
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  tests:
    timeout-minutes: 30
    name: Unit tests
    runs-on: ${{ matrix.os || 'ubuntu-latest' }}
    strategy:
      matrix:
        os: ["ubuntu-latest"]
        toxenv: [py]
        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14"]
        include:
          - python-version: "3.14"
            os: macos-latest
          - python-version: "3.12"
            toxenv: mypy-check
          - python-version: "pypy-3.9"
    env:
      TOXENV: ${{ matrix.toxenv || 'py' }}
    steps:
      - uses: actions/checkout@v5
 
      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: ${{ matrix.python-version }}
 
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install tox railroad-diagrams Jinja2
 
      - name: Test
        run: tox
 

What changed

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