Stale issues Bot workflow (adapter-hub/adapters)

The Stale issues Bot workflow from adapter-hub/adapters, explained and optimized by Latchkey.

What it does

This is the Stale issues Bot workflow from the adapter-hub/adapters 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: 'Stale issues Bot'

on:
  schedule:
    - cron: '0 6 * * *'

jobs:
  stale:
    runs-on: ubuntu-latest
    
    permissions:
      issues: write
    
    steps:
      - uses: actions/stale@v8
        with:
          repo-token: "${{ secrets.BOT_TOKEN }}"
          exempt-issue-labels: 'do-not-stale,enhancement,bug'
          stale-issue-message: 'This issue has been automatically marked as stale because it has been without activity for 90 days. This issue will be closed in 14 days unless you comment or remove the stale label.'
          close-issue-message: 'This issue was closed because it was stale for 14 days without any activity.'
          days-before-issue-stale: 90
          days-before-issue-close: 14
          days-before-pr-close: -1
          days-before-pr-stale: -1
          operations-per-run: 300

The same workflow, on Latchkey

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

name: 'Stale issues Bot'
 
on:
  schedule:
    - cron: '0 6 * * *'
 
jobs:
  stale:
    timeout-minutes: 30
    runs-on: latchkey-small
    
    permissions:
      issues: write
    
    steps:
      - uses: actions/stale@v8
        with:
          repo-token: "${{ secrets.BOT_TOKEN }}"
          exempt-issue-labels: 'do-not-stale,enhancement,bug'
          stale-issue-message: 'This issue has been automatically marked as stale because it has been without activity for 90 days. This issue will be closed in 14 days unless you comment or remove the stale label.'
          close-issue-message: 'This issue was closed because it was stale for 14 days without any activity.'
          days-before-issue-stale: 90
          days-before-issue-close: 14
          days-before-pr-close: -1
          days-before-pr-stale: -1
          operations-per-run: 300
 

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