Node CI workflow (SVG-Edit/svgedit)
The Node CI workflow from SVG-Edit/svgedit, explained and optimized by Latchkey.
CI health: D - needs work
Point runs-on at Latchkey and get caching, run de-duplication, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Node CI workflow from the SVG-Edit/svgedit 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: Node CI
on: [pull_request]
# To be able to write in the PR, we need write permission.
permissions:
pull-requests: write
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Use Node.js
uses: actions/setup-node@v3
with:
node-version: 20.x
- name: npm install, test and lint
run: |
npm ci
npm run build --workspace=packages/svgcanvas
npm run lint
npm run test
env:
CI: true
# - name: Report NYC coverage - removed for now
# uses: sidx1024/report-nyc-coverage-github-action@v1.2.6
# with:
# # Path to coverage file generated by "nyc report".
# coverage_file: "coverage/coverage-summary.json"
# base_coverage_file: "coverage/coverage-summary.json"
# comment_template_file: ".github/comment-template.md"
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: Node CI on: [pull_request] # To be able to write in the PR, we need write permission. permissions: pull-requests: write concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: runs-on: latchkey-small steps: - uses: actions/checkout@v3 - name: Use Node.js uses: actions/setup-node@v3 with: cache: 'npm' node-version: 20.x - name: npm install, test and lint run: | npm ci npm run build --workspace=packages/svgcanvas npm run lint npm run test env: CI: true # - name: Report NYC coverage - removed for now # uses: sidx1024/report-nyc-coverage-github-action@v1.2.6 # with: # # Path to coverage file generated by "nyc report". # coverage_file: "coverage/coverage-summary.json" # base_coverage_file: "coverage/coverage-summary.json" # comment_template_file: ".github/comment-template.md"
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.
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 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.