Build readme file workflow (neetcode-gh/leetcode)

The Build readme file workflow from neetcode-gh/leetcode, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get caching, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: neetcode-gh/leetcode.github/workflows/build-readme.ymlLicense MITView source

What it does

This is the Build readme file workflow from the neetcode-gh/leetcode 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

workflow (.yml)

name: Build readme file

on:
  workflow_dispatch:
  schedule:
    - cron: '0 * * * *' # Every hour

jobs:
  Build:
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [20.x]

    steps:
      - name: Checkout Repository
        uses: actions/checkout@v4
        with:
          ref: ${{ github.head_ref }}
          fetch-depth: 1

      - name: Use Node.js (dependency)
        uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}

      - name: Completion Table
        run: node updateCompletionTable.js;

      - name: Check for modified files
        id: git-check
        run: echo modified=$(if git diff-index --quiet HEAD --; then echo "false"; else echo "true"; fi) >> $GITHUB_OUTPUT

      - name: Push
        if: steps.git-check.outputs.modified == 'true'
        run: |
          git config --global user.email "71089234+Ahmad-A0@users.noreply.github.com"
          git config --global user.name "Bot-A0"
          git add .
          git commit -am "📜 Update README table (🛠️ from Github Actions)" || true
          git push || git pull --rebase && git push

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: Build readme file
 
on:
  workflow_dispatch:
  schedule:
    - cron: '0 * * * *' # Every hour
 
jobs:
  Build:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    strategy:
      matrix:
        node-version: [20.x]
 
    steps:
      - name: Checkout Repository
        uses: actions/checkout@v4
        with:
          ref: ${{ github.head_ref }}
          fetch-depth: 1
 
      - name: Use Node.js (dependency)
        uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: ${{ matrix.node-version }}
 
      - name: Completion Table
        run: node updateCompletionTable.js;
 
      - name: Check for modified files
        id: git-check
        run: echo modified=$(if git diff-index --quiet HEAD --; then echo "false"; else echo "true"; fi) >> $GITHUB_OUTPUT
 
      - name: Push
        if: steps.git-check.outputs.modified == 'true'
        run: |
          git config --global user.email "71089234+Ahmad-A0@users.noreply.github.com"
          git config --global user.name "Bot-A0"
          git add .
          git commit -am "📜 Update README table (🛠️ from Github Actions)" || true
          git push || git pull --rebase && git push

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.

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

actions/checkout actions/setup-node