CI workflow (select2/select2)
The CI workflow from select2/select2, explained and optimized by Latchkey.
CI health: F - at risk
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the CI workflow from the select2/select2 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: CI
on: [push, pull_request]
jobs:
docs:
name: Documentation
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- uses: astral-sh/setup-uv@v7
- run: uv run mkdocs build --strict
env:
MKDOCS_GIT_COMMITTERS_APIKEY: ${{ secrets.GITHUB_TOKEN }}
- uses: actions/upload-pages-artifact@v5
with:
path: site
linting:
name: Linting
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- name: Use Node.js 24
uses: actions/setup-node@v6
with:
node-version: 24
- name: npm install
run: npm install
- name: Run linting
run: grunt compile lint
tests:
name: Tests
runs-on: ubuntu-latest
steps:
- run: sudo apt update
- run: sudo apt install -y chromium-browser
- uses: actions/checkout@v7
- name: Use Node.js 24
uses: actions/setup-node@v6
with:
node-version: 24
- name: npm install
run: npm install
- name: Run tests
env:
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: "1"
PUPPETEER_EXECUTABLE_PATH: "/usr/bin/chromium-browser"
run: grunt compile test
minification:
name: Minification
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- name: Use Node.js 24
uses: actions/setup-node@v6
with:
node-version: 24
- name: npm install
run: npm install
- name: Run minification
run: grunt compile minify
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: CI on: [push, pull_request] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: docs: timeout-minutes: 30 name: Documentation runs-on: latchkey-small permissions: contents: read steps: - uses: actions/checkout@v7 with: fetch-depth: 0 - uses: astral-sh/setup-uv@v7 - run: uv run mkdocs build --strict env: MKDOCS_GIT_COMMITTERS_APIKEY: ${{ secrets.GITHUB_TOKEN }} - uses: actions/upload-pages-artifact@v5 with: path: site linting: timeout-minutes: 30 name: Linting runs-on: latchkey-small steps: - uses: actions/checkout@v7 - name: Use Node.js 24 uses: actions/setup-node@v6 with: cache: 'npm' node-version: 24 - name: npm install run: npm install - name: Run linting run: grunt compile lint tests: timeout-minutes: 30 name: Tests runs-on: latchkey-small steps: - run: sudo apt update - run: sudo apt install -y chromium-browser - uses: actions/checkout@v7 - name: Use Node.js 24 uses: actions/setup-node@v6 with: cache: 'npm' node-version: 24 - name: npm install run: npm install - name: Run tests env: PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: "1" PUPPETEER_EXECUTABLE_PATH: "/usr/bin/chromium-browser" run: grunt compile test minification: timeout-minutes: 30 name: Minification runs-on: latchkey-small steps: - uses: actions/checkout@v7 - name: Use Node.js 24 uses: actions/setup-node@v6 with: cache: 'npm' node-version: 24 - name: npm install run: npm install - name: Run minification run: grunt compile minify
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 useslatchkey-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.
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
This workflow runs 4 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.