Lock Issues workflow (pyca/pyopenssl)

The Lock Issues workflow from pyca/pyopenssl, explained and optimized by Latchkey.

What it does

This is the Lock Issues workflow from the pyca/pyopenssl 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: Lock Issues
on:
  schedule:
    - cron: '0 0 * * *'

permissions:
  issues: "write"

jobs:
  lock:
    runs-on: ubuntu-latest
    steps:
      - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          issue-inactive-days: 90
          pr-inactive-days: 90

The same workflow, on Latchkey

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

name: Lock Issues
on:
  schedule:
    - cron: '0 0 * * *'
 
permissions:
  issues: "write"
 
jobs:
  lock:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          issue-inactive-days: 90
          pr-inactive-days: 90
 

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.