Skip to content
Latchkey

Lint Code Base workflow (GoogleChrome/web-vitals)

The Lint Code Base workflow from GoogleChrome/web-vitals, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: GoogleChrome/web-vitals.github/workflows/lint.ymlLicense Apache-2.0View source

What it does

This is the Lint Code Base workflow from the GoogleChrome/web-vitals repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Lint Code Base
permissions:
  contents: read
on:
  pull_request:
  push:
    branches:
      - main
  workflow_dispatch:
jobs:
  lint:
    name: Lint Code Base
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v6
      - name: NPM install
        run: npm install
      - name: Run Prettier
        run: npm run format:check
      - name: Run ESlint
        run: npm run lint

The same workflow, on Latchkey

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

name: Lint Code Base
permissions:
  contents: read
on:
  pull_request:
  push:
    branches:
      - main
  workflow_dispatch:
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  lint:
    timeout-minutes: 30
    name: Lint Code Base
    runs-on: latchkey-small
    steps:
      - name: Checkout Code
        uses: actions/checkout@v6
      - name: NPM install
        run: npm install
      - name: Run Prettier
        run: npm run format:check
      - name: Run ESlint
        run: npm run lint
 

What changed

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:

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