Enforce pnpm workflow (braintrustdata/autoevals)

The Enforce pnpm workflow from braintrustdata/autoevals, explained and optimized by Latchkey.

What it does

This is the Enforce pnpm workflow from the braintrustdata/autoevals 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: Enforce pnpm

on:
  pull_request:
  push:
    branches: [main]

jobs:
  reject-npm-lockfile:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      - name: Reject npm lockfiles
        run: |
          if git ls-files | grep -E '(^|/)package-lock\.json$'; then
            echo "Remove package-lock.json and use pnpm."
            exit 1
          fi

The same workflow, on Latchkey

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

name: Enforce pnpm
 
on:
  pull_request:
  push:
    branches: [main]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  reject-npm-lockfile:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      - name: Reject npm lockfiles
        run: |
          if git ls-files | grep -E '(^|/)package-lock\.json$'; then
            echo "Remove package-lock.json and use pnpm."
            exit 1
          fi
 

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.
• Add a job timeout so a hung step cannot burn hours of runner time.

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