Lint workflow (hsahovic/poke-env)
The Lint workflow from hsahovic/poke-env, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get caching, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Lint workflow from the hsahovic/poke-env 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: Lint
on:
push:
branches:
- "master"
pull_request:
branches:
- "master"
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
jobs:
lint:
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- name: Checkout repository code
uses: actions/checkout@v7
# Setup Python (faster than using Python container)
- name: Setup Python
uses: actions/setup-python@v6
with:
python-version: "3.14"
- name: Setup uv
uses: astral-sh/setup-uv@v7
with:
enable-cache: true
- name: Install dependencies
run: uv sync --dev
- name: Download Pandoc
run: |
wget https://github.com/jgm/pandoc/releases/download/3.1.9/pandoc-3.1.9-linux-amd64.tar.gz
tar xvzf pandoc-3.1.9-linux-amd64.tar.gz --strip-components 2 -C /usr/local/bin
- name: Run black
run: uv run black --check src/ unit_tests/ integration_tests/
- name: Run flake8
run: uv run flake8 src/ unit_tests/ integration_tests/
- name: Run isort
run: uv run isort --check .
- name: Run mypy
run: uv run mypy src
- name: Validate docs links
run: uv run python scripts/check_docs_links.py
- name: Build docs (strict)
run: |
LC_ALL=C LANG=C uv run python -m sphinx -b html -W docs/source docs/_build/html
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: Lint on: push: branches: - "master" pull_request: branches: - "master" concurrency: group: ${{ github.workflow }}-${{ github.ref }} jobs: lint: runs-on: latchkey-small timeout-minutes: 10 steps: - name: Checkout repository code uses: actions/checkout@v7 # Setup Python (faster than using Python container) - name: Setup Python uses: actions/setup-python@v6 with: cache: 'pip' python-version: "3.14" - name: Setup uv uses: astral-sh/setup-uv@v7 with: enable-cache: true - name: Install dependencies run: uv sync --dev - name: Download Pandoc run: | wget https://github.com/jgm/pandoc/releases/download/3.1.9/pandoc-3.1.9-linux-amd64.tar.gz tar xvzf pandoc-3.1.9-linux-amd64.tar.gz --strip-components 2 -C /usr/local/bin - name: Run black run: uv run black --check src/ unit_tests/ integration_tests/ - name: Run flake8 run: uv run flake8 src/ unit_tests/ integration_tests/ - name: Run isort run: uv run isort --check . - name: Run mypy run: uv run mypy src - name: Validate docs links run: uv run python scripts/check_docs_links.py - name: Build docs (strict) run: | LC_ALL=C LANG=C uv run python -m sphinx -b html -W docs/source docs/_build/html
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 useslatchkey-small; pick the runner size that fits the job. - Cache dependency installs on the setup step so they are served from cache.
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:
- Network fetches
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.