Test workflow (wenzhixin/bootstrap-table)

The Test workflow from wenzhixin/bootstrap-table, explained and optimized by Latchkey.

What it does

This is the Test workflow from the wenzhixin/bootstrap-table 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

on:
  pull_request:

jobs:
  changes:
    runs-on: ubuntu-latest
    outputs:
      site: ${{ steps.filter.outputs.site }}
    steps:
      - uses: actions/checkout@v4
      - uses: dorny/paths-filter@v3
        id: filter
        with:
          filters: |
            site:
              - 'site/**'
              - 'yarn.lock'

  test:
    needs: changes
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: 24
          cache: 'yarn'

      - uses: actions/checkout@v4
        with:
          repository: 'wenzhixin/bootstrap-table-examples'
          path: './tools/bootstrap-table-examples'

      - name: Lint src and check docs
        run: |
          yarn install --frozen-lockfile
          yarn pre-commit

      - name: Lint and build site
        if: needs.changes.outputs.site == 'true'
        run: |
          cd site
          yarn install --frozen-lockfile
          yarn lint
          yarn build

      - name: Cypress Test
        run: |
          mv ./tools/bootstrap-table-examples cypress/html
          yarn css:build:src
          yarn test

The same workflow, on Latchkey

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

name: Test
 
on:
  pull_request:
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  changes:
    timeout-minutes: 30
    runs-on: latchkey-small
    outputs:
      site: ${{ steps.filter.outputs.site }}
    steps:
      - uses: actions/checkout@v4
      - uses: dorny/paths-filter@v3
        id: filter
        with:
          filters: |
            site:
              - 'site/**'
              - 'yarn.lock'
 
  test:
    timeout-minutes: 30
    needs: changes
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
 
      - uses: actions/setup-node@v4
        with:
          node-version: 24
          cache: 'yarn'
 
      - uses: actions/checkout@v4
        with:
          repository: 'wenzhixin/bootstrap-table-examples'
          path: './tools/bootstrap-table-examples'
 
      - name: Lint src and check docs
        run: |
          yarn install --frozen-lockfile
          yarn pre-commit
 
      - name: Lint and build site
        if: needs.changes.outputs.site == 'true'
        run: |
          cd site
          yarn install --frozen-lockfile
          yarn lint
          yarn build
 
      - name: Cypress Test
        run: |
          mv ./tools/bootstrap-table-examples cypress/html
          yarn css:build:src
          yarn test
 

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.

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:

• Dependency installs
• End-to-end and browser tests

This workflow runs 2 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