Mark and maybe close stale issues and PRs workflow (kmkurn/pytorch-crf)

The Mark and maybe close stale issues and PRs workflow from kmkurn/pytorch-crf, explained and optimized by Latchkey.

What it does

This is the Mark and maybe close stale issues and PRs workflow from the kmkurn/pytorch-crf 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: 'Mark and maybe close stale issues and PRs'

on:
  workflow_dispatch:
  schedule:
    - cron: '30 1 * * *'
    
jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v4
        with:
          days-before-stale: 90  # 3 months
          days-before-close: 30
          operations-per-run: 60

The same workflow, on Latchkey

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

name: 'Mark and maybe close stale issues and PRs'
 
on:
  workflow_dispatch:
  schedule:
    - cron: '30 1 * * *'
    
jobs:
  stale:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/stale@v4
        with:
          days-before-stale: 90  # 3 months
          days-before-close: 30
          operations-per-run: 60
 

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.

Actions used in this workflow