Test WebKit workflow (sweetalert2/sweetalert2)

The Test WebKit workflow from sweetalert2/sweetalert2, explained and optimized by Latchkey.

What it does

This is the Test WebKit workflow from the sweetalert2/sweetalert2 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: Test WebKit

on:
  push:
    branches:
      - main

jobs:
  WebKit:
    runs-on: macos-latest
    timeout-minutes: 10

    steps:
      - uses: actions/checkout@v5
      - uses: oven-sh/setup-bun@v2

      - run: bun install

      - run: bun run build

      - run: bun run test --browser webkit

The same workflow, on Latchkey

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

name: Test WebKit
 
on:
  push:
    branches:
      - main
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  WebKit:
    runs-on: macos-latest
    timeout-minutes: 10
 
    steps:
      - uses: actions/checkout@v5
      - uses: oven-sh/setup-bun@v2
 
      - run: bun install
 
      - run: bun run build
 
      - run: bun run test --browser webkit
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.

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