Tests: pretest/posttest workflow (tape-testing/tape)

The Tests: pretest/posttest workflow from tape-testing/tape, explained and optimized by Latchkey.

What it does

This is the Tests: pretest/posttest workflow from the tape-testing/tape 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: 'Tests: pretest/posttest'

on: [pull_request, push]

permissions:
  contents: read

jobs:
  tests:
    uses: ljharb/actions/.github/workflows/pretest.yml@main
    with:
      skip-engines: true # bin/tape requires node 8+, but the rest of tape supports 0.4+

The same workflow, on Latchkey

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

name: 'Tests: pretest/posttest'
 
on: [pull_request, push]
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  tests:
    timeout-minutes: 30
    uses: ljharb/actions/.github/workflows/pretest.yml@main
    with:
      skip-engines: true # bin/tape requires node 8+, but the rest of tape supports 0.4+
 

What changed

• 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.

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.