Code quality workflow (tomasvotava/fastapi-sso)

The Code quality workflow from tomasvotava/fastapi-sso, explained and optimized by Latchkey.

What it does

This is the Code quality workflow from the tomasvotava/fastapi-sso 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: Code quality

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
    steps:
      - uses: actions/checkout@v3
      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v3
        with:
          python-version: ${{ matrix.python-version }}
      - name: Install pipx
        run: python -m pip install pipx && python -m pipx ensurepath
      - name: Install poetry
        run: pipx install poetry && poetry --version
      - name: Install dependencies
        run: |
          POETRY_VIRTUALENVS_CREATE=false poetry install
      - name: Analysing the code with ruff
        run: poetry run poe ruff
      - name: Static type-checking using mypy
        run: poetry run poe mypy
      - name: Format checking using black
        run: poetry run poe black-check
      - name: Format checking using isort
        run: poetry run poe isort-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: Code quality
 
on: [push, pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  lint:
    timeout-minutes: 30
    runs-on: latchkey-small
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
    steps:
      - uses: actions/checkout@v3
      - name: Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@v3
        with:
          cache: 'pip'
          python-version: ${{ matrix.python-version }}
      - name: Install pipx
        run: python -m pip install pipx && python -m pipx ensurepath
      - name: Install poetry
        run: pipx install poetry && poetry --version
      - name: Install dependencies
        run: |
          POETRY_VIRTUALENVS_CREATE=false poetry install
      - name: Analysing the code with ruff
        run: poetry run poe ruff
      - name: Static type-checking using mypy
        run: poetry run poe mypy
      - name: Format checking using black
        run: poetry run poe black-check
      - name: Format checking using isort
        run: poetry run poe isort-check
 

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.

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 1 job (5 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