pre-commit workflow (tensorflow/transform)

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

What it does

This is the pre-commit workflow from the tensorflow/transform repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: pre-commit

on:
  pull_request:
  push:
     branches: [master]

jobs:
  pre-commit:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4.1.7
      with:
        # Ensure the full history is fetched
        # This is required to run pre-commit on a specific set of commits
        # TODO: Remove this when all the pre-commit issues are fixed
        fetch-depth: 0
    - uses: actions/setup-python@v5.1.1
      with:
        python-version: 3.13
    - uses: pre-commit/action@v3.0.1

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: pre-commit
 
on:
  pull_request:
  push:
     branches: [master]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  pre-commit:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - uses: actions/checkout@v4.1.7
      with:
        # Ensure the full history is fetched
        # This is required to run pre-commit on a specific set of commits
        # TODO: Remove this when all the pre-commit issues are fixed
        fetch-depth: 0
    - uses: actions/setup-python@v5.1.1
      with:
        cache: 'pip'
        python-version: 3.13
    - uses: pre-commit/action@v3.0.1
 

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.

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 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow