Build & Test workflow (melonjs/melonJS)

The Build & Test workflow from melonjs/melonJS, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get caching, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: melonjs/melonJS.github/workflows/main.ymlLicense MITView source

What it does

This is the Build & Test workflow from the melonjs/melonJS 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

workflow (.yml)

name: Build & Test
# Runs lint + test on every push/PR - no path-filtered shim partition.
# The previous two-workflow setup (`main.yml` + `main-docs.yml`) was
# racy on mixed PRs (PRs touching both `.md` and code): GitHub Actions
# evaluates `paths` / `paths-ignore` against the full PR diff, so a
# mixed PR triggered BOTH workflows, they shared `concurrency.group`,
# and the faster docs-shim cancelled the real CI run while still
# reporting green checks. Docs-only PRs pay ~2 minutes of CI cost as
# the trade-off; cheaper than silently merging a lint failure.
on:
  push:
    branches: [master]
  pull_request:
    types: [opened, synchronize]

concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: true

permissions:
  contents: read

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm lint
      - run: pnpm biome check
      - run: pnpm build

  test:
    needs: lint
    runs-on: ubuntu-latest
    container:
      # must match the workspace's playwright version (root devDependencies)
      image: mcr.microsoft.com/playwright:v1.61.1-noble
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm test
      - run: pnpm -F @melonjs/matter-adapter test
      - run: pnpm -F @melonjs/planck-adapter test

  # Windows build - only on master push, not on PRs
  windows:
    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        shell: bash
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm lint
      - run: pnpm build

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: Build & Test
# Runs lint + test on every push/PR - no path-filtered shim partition.
# The previous two-workflow setup (`main.yml` + `main-docs.yml`) was
# racy on mixed PRs (PRs touching both `.md` and code): GitHub Actions
# evaluates `paths` / `paths-ignore` against the full PR diff, so a
# mixed PR triggered BOTH workflows, they shared `concurrency.group`,
# and the faster docs-shim cancelled the real CI run while still
# reporting green checks. Docs-only PRs pay ~2 minutes of CI cost as
# the trade-off; cheaper than silently merging a lint failure.
on:
  push:
    branches: [master]
  pull_request:
    types: [opened, synchronize]
 
concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: true
 
permissions:
  contents: read
 
jobs:
  lint:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm lint
      - run: pnpm biome check
      - run: pnpm build
 
  test:
    timeout-minutes: 30
    needs: lint
    runs-on: latchkey-small
    container:
      # must match the workspace's playwright version (root devDependencies)
      image: mcr.microsoft.com/playwright:v1.61.1-noble
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm test
      - run: pnpm -F @melonjs/matter-adapter test
      - run: pnpm -F @melonjs/planck-adapter test
 
  # Windows build - only on master push, not on PRs
  windows:
    timeout-minutes: 30
    if: github.event_name == 'push' && github.ref == 'refs/heads/master'
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v5
      - name: Setup node
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
      - uses: pnpm/action-setup@v5
      - name: Get pnpm store directory
        shell: bash
        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
      - uses: actions/cache@v5
        with:
          path: ${{ env.STORE_PATH }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: ${{ runner.os }}-pnpm-store-
      - run: pnpm i
      - run: pnpm lint
      - run: pnpm build

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

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:

End-to-end and browser tests

This workflow runs 3 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/setup-node pnpm/action-setup actions/cache