check-cla workflow (CesiumGS/cesium)

The check-cla workflow from CesiumGS/cesium, explained and optimized by Latchkey.

What it does

This is the check-cla workflow from the CesiumGS/cesium repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

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

The workflow

name: check-cla
on:
  pull_request_target:
    types: [opened]

jobs:
  check-cla:
    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write
    steps:
      - uses: actions/checkout@v7
      - name: install node 22
        uses: actions/setup-node@v6
        with:
          node-version: '22'
      - name: install npm packages
        working-directory: ./.github/actions/check-for-CLA
        run: npm install
      - name: run script
        working-directory: ./.github/actions/check-for-CLA
        run: node index.js
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          PULL_REQUEST_ID: ${{ github.event.number }}
          GOOGLE_KEYS: ${{ secrets.GOOGLE_KEYS }}
          INDIVIDUAL_CLA_SHEET_ID: ${{ secrets.INDIVIDUAL_CLA_SHEET_ID }}
          CORPORATE_CLA_SHEET_ID: ${{ secrets.CORPORATE_CLA_SHEET_ID }}

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: check-cla
on:
  pull_request_target:
    types: [opened]
 
jobs:
  check-cla:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: write
    steps:
      - uses: actions/checkout@v7
      - name: install node 22
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: '22'
      - name: install npm packages
        working-directory: ./.github/actions/check-for-CLA
        run: npm install
      - name: run script
        working-directory: ./.github/actions/check-for-CLA
        run: node index.js
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          PULL_REQUEST_ID: ${{ github.event.number }}
          GOOGLE_KEYS: ${{ secrets.GOOGLE_KEYS }}
          INDIVIDUAL_CLA_SHEET_ID: ${{ secrets.INDIVIDUAL_CLA_SHEET_ID }}
          CORPORATE_CLA_SHEET_ID: ${{ secrets.CORPORATE_CLA_SHEET_ID }}
 

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.
• 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.

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