Lock Threads workflow (webtorrent/webtorrent)

The Lock Threads workflow from webtorrent/webtorrent, explained and optimized by Latchkey.

What it does

This is the Lock Threads workflow from the webtorrent/webtorrent 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

name: 'Lock Threads'

on:
  schedule:
    - cron: '0 13 * * *'
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

concurrency:
  group: lock

jobs:
  action:
    runs-on: ubuntu-latest
    steps:
      - uses: dessant/lock-threads@v6

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 13 * * *'
  workflow_dispatch:
 
permissions:
  issues: write
  pull-requests: write
 
concurrency:
  group: lock
 
jobs:
  action:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: dessant/lock-threads@v6
 

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.

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