Validate PR YAML Files workflow (awesome-opencode/awesome-opencode)

The Validate PR YAML Files workflow from awesome-opencode/awesome-opencode, explained and optimized by Latchkey.

What it does

This is the Validate PR YAML Files workflow from the awesome-opencode/awesome-opencode repository, a real project running GitHub Actions. It is shown here with attribution under its CC0-1.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Validate PR YAML Files

on:
  pull_request:
    paths:
      - 'data/**'

permissions:
  contents: read

jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

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

      - name: Install dependencies
        run: npm ci

      - name: Get changed YAML files
        id: changed-files
        uses: tj-actions/changed-files@v44
        with:
          files: |
            data/**/*.yaml

      - name: Validate YAML files
        run: |
          if [[ -n "${{ steps.changed-files.outputs.all_changed_files }}" ]]; then
            node scripts/validate.js ${{ steps.changed-files.outputs.all_changed_files }}
          else
            echo "No YAML files changed, skipping validation"
          fi

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: Validate PR YAML Files
 
on:
  pull_request:
    paths:
      - 'data/**'
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  validate:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
 
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: '20'
 
      - name: Install dependencies
        run: npm ci
 
      - name: Get changed YAML files
        id: changed-files
        uses: tj-actions/changed-files@v44
        with:
          files: |
            data/**/*.yaml
 
      - name: Validate YAML files
        run: |
          if [[ -n "${{ steps.changed-files.outputs.all_changed_files }}" ]]; then
            node scripts/validate.js ${{ steps.changed-files.outputs.all_changed_files }}
          else
            echo "No YAML files changed, skipping validation"
          fi
 

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.

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.

Actions used in this workflow