Skip to content
Latchkey

Python Lint and Test workflow (mietzen/porkbun-ddns)

The Python Lint and Test workflow from mietzen/porkbun-ddns, explained and optimized by Latchkey.

D

CI health: D - needs work

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: mietzen/porkbun-ddns.github/workflows/lint_and_test.ymlLicense MITView source

What it does

This is the Python Lint and Test workflow from the mietzen/porkbun-ddns 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: Python Lint and Test

on:
  pull_request:
    branches:
      - 'main'

jobs:
  Test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
      fail-fast: false

    steps:
      - uses: actions/checkout@v7
      - 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
          pip install ruff pytest
          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
      - name: Test with pytest
        run: |
          pytest ./porkbun_ddns/test
      - name: Lint with ruff
        env: 
          PY_VER: ${{ matrix.python-version }}
        run: |
          # stop the build if there are Python syntax errors or undefined names
          PY_VER=$(echo py${PY_VER} | tr -d '.')
          ruff check --output-format=github --ignore=E501 --exclude=__init__.py --target-version=${PY_VER} ./porkbun_ddns

  Check-Test:
    if: ${{ always() }}
    runs-on: ubuntu-latest
    needs:
      - Test
    steps:
      - run: |
          result="${{ needs.Test.result }}"
          if [[ $result == "success" || $result == "skipped" ]]; then
            exit 0
          else
            exit 1
          fi

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: Python Lint and Test
 
on:
  pull_request:
    branches:
      - 'main'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  Test:
    timeout-minutes: 30
    runs-on: latchkey-small
    strategy:
      matrix:
        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
      fail-fast: false
 
    steps:
      - uses: actions/checkout@v7
      - 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
          pip install ruff pytest
          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
      - name: Test with pytest
        run: |
          pytest ./porkbun_ddns/test
      - name: Lint with ruff
        env: 
          PY_VER: ${{ matrix.python-version }}
        run: |
          # stop the build if there are Python syntax errors or undefined names
          PY_VER=$(echo py${PY_VER} | tr -d '.')
          ruff check --output-format=github --ignore=E501 --exclude=__init__.py --target-version=${PY_VER} ./porkbun_ddns
 
  Check-Test:
    timeout-minutes: 30
    if: ${{ always() }}
    runs-on: latchkey-small
    needs:
      - Test
    steps:
      - run: |
          result="${{ needs.Test.result }}"
          if [[ $result == "success" || $result == "skipped" ]]; then
            exit 0
          else
            exit 1
          fi
 

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 2 jobs (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