main workflow (pre-commit/pre-commit)

The main workflow from pre-commit/pre-commit, explained and optimized by Latchkey.

What it does

This is the main workflow from the pre-commit/pre-commit 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: main

on:
  push:
    branches: [main, test-me-*]
    tags: '*'
  pull_request:

concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
  cancel-in-progress: true

jobs:
  main-windows:
    uses: asottile/workflows/.github/workflows/tox.yml@v1.8.1
    with:
      env: '["py310"]'
      os: windows-latest
  main-linux:
    uses: asottile/workflows/.github/workflows/tox.yml@v1.8.1
    with:
      env: '["py310", "py311", "py312", "py313"]'
      os: ubuntu-latest

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: main
 
on:
  push:
    branches: [main, test-me-*]
    tags: '*'
  pull_request:
 
concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
  cancel-in-progress: true
 
jobs:
  main-windows:
    timeout-minutes: 30
    uses: asottile/workflows/.github/workflows/tox.yml@v1.8.1
    with:
      env: '["py310"]'
      os: windows-latest
  main-linux:
    timeout-minutes: 30
    uses: asottile/workflows/.github/workflows/tox.yml@v1.8.1
    with:
      env: '["py310", "py311", "py312", "py313"]'
      os: ubuntu-latest
 

What changed

• Add a job timeout so a hung step cannot burn hours of runner time.

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.

This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.