Sample List Generator workflow (GoogleChrome/chrome-extensions-samples)

The Sample List Generator workflow from GoogleChrome/chrome-extensions-samples, explained and optimized by Latchkey.

What it does

This is the Sample List Generator workflow from the GoogleChrome/chrome-extensions-samples 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

name: Sample List Generator
on:
  push:
    branches:
      - main

defaults:
  run:
    working-directory: ./.repo/sample-list-generator

jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 18

      - name: Install dependencies
        run: npm install

      - name: Generate sample list
        run: npm run start

      - name: Upload to artifacts
        uses: actions/upload-artifact@v4
        with:
          name: extension-samples.json
          path: ./.repo/sample-list-generator/extension-samples.json
          if-no-files-found: error

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: Sample List Generator
on:
  push:
    branches:
      - main
 
defaults:
  run:
    working-directory: ./.repo/sample-list-generator
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  generate:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
 
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: 18
 
      - name: Install dependencies
        run: npm install
 
      - name: Generate sample list
        run: npm run start
 
      - name: Upload to artifacts
        uses: actions/upload-artifact@v4
        with:
          name: extension-samples.json
          path: ./.repo/sample-list-generator/extension-samples.json
          if-no-files-found: error
 

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.

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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow