Lock Threads workflow (final-form/react-final-form)

The Lock Threads workflow from final-form/react-final-form, explained and optimized by Latchkey.

CI health: A - excellent

Point runs-on at Latchkey and get 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: final-form/react-final-form.github/workflows/lock.ymlLicense MITView source

What it does

This is the Lock Threads workflow from the final-form/react-final-form 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: "Lock Threads"

on:
  schedule:
    - cron: "0 * * * *"
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

concurrency:
  group: lock

jobs:
  action:
    runs-on: ubuntu-latest
    steps:
      # dessant/lock-threads pinned to commit 89ae32b08ed1a541efecbab17912962a5e38981c
      - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c
        with:
          process-only: "issues, prs"
          issue-inactive-days: "365"
          issue-lock-reason: "resolved"
          pr-inactive-days: "365"
          pr-lock-reason: "resolved"

The same workflow, on Latchkey

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

name: "Lock Threads"
 
on:
  schedule:
    - cron: "0 * * * *"
  workflow_dispatch:
 
permissions:
  issues: write
  pull-requests: write
 
concurrency:
  group: lock
 
jobs:
  action:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      # dessant/lock-threads pinned to commit 89ae32b08ed1a541efecbab17912962a5e38981c
      - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c
        with:
          process-only: "issues, prs"
          issue-inactive-days: "365"
          issue-lock-reason: "resolved"
          pr-inactive-days: "365"
          pr-lock-reason: "resolved"

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.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.