Stale Issue Handler workflow (brentvollebregt/auto-py-to-exe)

The Stale Issue Handler workflow from brentvollebregt/auto-py-to-exe, 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: brentvollebregt/auto-py-to-exe.github/workflows/stale.ymlLicense MITView source

What it does

This is the Stale Issue Handler workflow from the brentvollebregt/auto-py-to-exe 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: Stale Issue Handler
on:
  workflow_dispatch:
  schedule:
    - cron: '0 0 * * *'

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v10
        with:
          stale-issue-message: 'This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.'
          close-issue-message: 'Closing issue due to no activity in more than 60 days.'
          days-before-stale: 30
          days-before-close: 5
          exempt-issue-labels: 'blocked,keep'

The same workflow, on Latchkey

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

name: Stale Issue Handler
on:
  workflow_dispatch:
  schedule:
    - cron: '0 0 * * *'
 
jobs:
  stale:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/stale@v10
        with:
          stale-issue-message: 'This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.'
          close-issue-message: 'Closing issue due to no activity in more than 60 days.'
          days-before-stale: 30
          days-before-close: 5
          exempt-issue-labels: 'blocked,keep'

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

actions/stale