CI workflow (FormidableLabs/webpack-dashboard)

The CI workflow from FormidableLabs/webpack-dashboard, explained and optimized by Latchkey.

What it does

This is the CI workflow from the FormidableLabs/webpack-dashboard 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: CI

on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master

jobs:
  build:

    runs-on: ${{ matrix.os }}

    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest]
        node-version: [18.x]

    steps:
    # Setup
    - uses: actions/checkout@v4
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v4
      with:
        cache: "yarn"
        node-version: ${{ matrix.node-version }}

    # Installation
    - run: yarn --version
    - run: yarn install --frozen-lockfile
      env:
        CI: true

    # CI
    - run: yarn check-ci
    # Test
    - run: yarn test
    # Code coverage
    - run: yarn codecov

The same workflow, on Latchkey

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

name: CI
 
on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
 
    runs-on: ${{ matrix.os }}
 
    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest]
        node-version: [18.x]
 
    steps:
    # Setup
    - uses: actions/checkout@v4
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v4
      with:
        cache: "yarn"
        node-version: ${{ matrix.node-version }}
 
    # Installation
    - run: yarn --version
    - run: yarn install --frozen-lockfile
      env:
        CI: true
 
    # CI
    - run: yarn check-ci
    # Test
    - run: yarn test
    # Code coverage
    - run: yarn codecov
 

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.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 1 job (2 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow