Skip to content
Latchkey

CI workflow (simonwep/pickr)

The CI workflow from simonwep/pickr, explained and optimized by Latchkey.

C

CI health: C - fair

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

Grade your own workflow free or run it on Latchkey →
Source: simonwep/pickr.github/workflows/ci.ymlLicense MITView source

What it does

This is the CI workflow from the simonwep/pickr 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

workflow (.yml)
name: CI

on: [ "push", "pull_request" ]

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

            -   name: Setup pnpm
                uses: pnpm/action-setup@v3
                with:
                    version: 9.0.6

            -   name: Set up Node.js
                uses: actions/setup-node@v4
                with:
                    node-version: 20
                    cache: 'pnpm'

            -   name: Install dependencies
                run: pnpm install --frozen-lockfile

            -   name: Lint
                run: pnpm run lint

            -   name: Build
                run: pnpm run build

            -   name: Bundle files for deployment
                run: tar -cvf github-pages.tar dist www index.html

            -   name: Upload artifact for deployment
                uses: actions/upload-artifact@v4
                with:
                    name: github-pages
                    path: github-pages.tar

    deploy:
        name: Deploy to GitHub Pages
        needs: build
        permissions:
            pages: write
            id-token: write
        environment:
            name: github-pages
            url: ${{ steps.deployment.outputs.page_url }}
        runs-on: ubuntu-latest
        steps:
            -   name: Deploy to GitHub Pages
                uses: actions/deploy-pages@v4

The same workflow, on Latchkey

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

name: CI
 
on: [ "push", "pull_request" ]
 
concurrency:
    group: ${{ github.workflow }}-${{ github.ref }}
    cancel-in-progress: true
 
jobs:
    build:
        timeout-minutes: 30
        name: Lint and build
        runs-on: latchkey-small
        steps:
            -   name: Checkout repository
                uses: actions/checkout@v4
 
            -   name: Setup pnpm
                uses: pnpm/action-setup@v3
                with:
                    version: 9.0.6
 
            -   name: Set up Node.js
                uses: actions/setup-node@v4
                with:
                    node-version: 20
                    cache: 'pnpm'
 
            -   name: Install dependencies
                run: pnpm install --frozen-lockfile
 
            -   name: Lint
                run: pnpm run lint
 
            -   name: Build
                run: pnpm run build
 
            -   name: Bundle files for deployment
                run: tar -cvf github-pages.tar dist www index.html
 
            -   name: Upload artifact for deployment
                uses: actions/upload-artifact@v4
                with:
                    name: github-pages
                    path: github-pages.tar
 
    deploy:
        timeout-minutes: 30
        name: Deploy to GitHub Pages
        needs: build
        permissions:
            pages: write
            id-token: write
        environment:
            name: github-pages
            url: ${{ steps.deployment.outputs.page_url }}
        runs-on: latchkey-small
        steps:
            -   name: Deploy to GitHub Pages
                uses: actions/deploy-pages@v4
 

What changed

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:

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