Lock Inactive Issues workflow (pndurette/gTTS)

The Lock Inactive Issues workflow from pndurette/gTTS, explained and optimized by Latchkey.

What it does

This is the Lock Inactive Issues workflow from the pndurette/gTTS 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 Inactive Issues'

on:
  schedule:
    # Every day at 6 AM
    - cron: '0 6 * * *'

jobs:
  lock:
    runs-on: ubuntu-latest
    steps:
      - uses: dessant/lock-threads@v5
        with:
          github-token: ${{ github.token }}
          issue-inactive-days: '15'
          process-only: 'issues'

The same workflow, on Latchkey

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

name: 'Lock Inactive Issues'
 
on:
  schedule:
    # Every day at 6 AM
    - cron: '0 6 * * *'
 
jobs:
  lock:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: dessant/lock-threads@v5
        with:
          github-token: ${{ github.token }}
          issue-inactive-days: '15'
          process-only: 'issues'
 

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.