Lint workflow (blocks/blocks)

The Lint workflow from blocks/blocks, explained and optimized by Latchkey.

What it does

This is the Lint workflow from the blocks/blocks 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: Lint

on: [push, pull_request]

jobs:
  build-and-lint:
    name: Lint
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@master

      - name: Set up Node.js 12.x
        uses: actions/setup-node@master
        with:
          node-version:  12.x

      - name: Install
        run: yarn

      - name: Lint
        run: yarn lint

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: Lint
 
on: [push, pull_request]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build-and-lint:
    timeout-minutes: 30
    name: Lint
    runs-on: latchkey-small
    steps:
      - name: Checkout
        uses: actions/checkout@master
 
      - name: Set up Node.js 12.x
        uses: actions/setup-node@master
        with:
          cache: 'npm'
          node-version:  12.x
 
      - name: Install
        run: yarn
 
      - name: Lint
        run: yarn lint
 

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

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