Copilot Setup Steps workflow (Ripple-TS/ripple)

The Copilot Setup Steps workflow from Ripple-TS/ripple, explained and optimized by Latchkey.

What it does

This is the Copilot Setup Steps workflow from the Ripple-TS/ripple 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

# GitHub Copilot agent environment setup
# See: https://gh.io/copilot/actions-setup-steps

name: Copilot Setup Steps

on: workflow_dispatch

jobs:
  copilot-setup-steps:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v6

      - name: Install pnpm
        uses: pnpm/action-setup@v6

      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: "24"
          cache: "pnpm"

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

      - name: Build CLI
        working-directory: ./packages/cli
        run: pnpm build

      - name: Build ESLint parser
        working-directory: ./packages/eslint-parser
        run: pnpm build

      - name: Sync agent configurations
        run: pnpm agents:sync

The same workflow, on Latchkey

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

# GitHub Copilot agent environment setup
# See: https://gh.io/copilot/actions-setup-steps
 
name: Copilot Setup Steps
 
on: workflow_dispatch
 
jobs:
  copilot-setup-steps:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Checkout code
        uses: actions/checkout@v6
 
      - name: Install pnpm
        uses: pnpm/action-setup@v6
 
      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: "24"
          cache: "pnpm"
 
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
 
      - name: Build CLI
        working-directory: ./packages/cli
        run: pnpm build
 
      - name: Build ESLint parser
        working-directory: ./packages/eslint-parser
        run: pnpm build
 
      - name: Sync agent configurations
        run: pnpm agents:sync
 

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