autofix.ci # needed to securely identify the workflow workflow (sindresorhus/eslint-plugin-unicorn)
The autofix.ci # needed to securely identify the workflow workflow from sindresorhus/eslint-plugin-unicorn, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the autofix.ci # needed to securely identify the workflow workflow from the sindresorhus/eslint-plugin-unicorn 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: autofix.ci # needed to securely identify the workflow
on:
pull_request:
permissions: {}
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
update-snapshots:
if: github.repository == 'sindresorhus/eslint-plugin-unicorn'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
# Locked due to the difference of `zlib.gzipSync()` between Node.js versions
node-version: 24
- run: npm install --legacy-peer-deps
- run: npm run lint
- run: rm -rf test/snapshots
# Force update snapshots, https://github.com/avajs/ava/discussions/2754
- run: npx ava --update-snapshots
env:
AVA_FORCE_CI: not-ci
- uses: autofix-ci/action@v1
with:
commit-message: "Update snapshots"
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: autofix.ci # needed to securely identify the workflow on: pull_request: permissions: {} concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: update-snapshots: timeout-minutes: 30 if: github.repository == 'sindresorhus/eslint-plugin-unicorn' runs-on: latchkey-small steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: cache: 'npm' # Locked due to the difference of `zlib.gzipSync()` between Node.js versions node-version: 24 - run: npm install --legacy-peer-deps - run: npm run lint - run: rm -rf test/snapshots # Force update snapshots, https://github.com/avajs/ava/discussions/2754 - run: npx ava --update-snapshots env: AVA_FORCE_CI: not-ci - uses: autofix-ci/action@v1 with: commit-message: "Update snapshots"
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. - 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 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.