Stale Issue Handler workflow (brookhong/Surfingkeys)
The Stale Issue Handler workflow from brookhong/Surfingkeys, explained and optimized by Latchkey.
A
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.
What it does
This is the Stale Issue Handler workflow from the brookhong/Surfingkeys 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:
schedule:
- cron: '0 2 * * *'
permissions:
issues: write
pull-requests: write
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-label: stale
stale-issue-message: >
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed in 14 days if no further activity occurs.
days-before-issue-stale: 180
days-before-issue-close: 14
stale-pr-label: stale
stale-pr-message: >
This PR has been automatically marked as stale because it has not had
recent activity. It will be closed in 14 days if no further activity occurs.
days-before-pr-stale: 90
days-before-pr-close: 14
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Stale Issue Handler on: schedule: - cron: '0 2 * * *' permissions: issues: write pull-requests: write jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/stale@v9 with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-label: stale stale-issue-message: > This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. days-before-issue-stale: 180 days-before-issue-close: 14 stale-pr-label: stale stale-pr-message: > This PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. days-before-pr-stale: 90 days-before-pr-close: 14
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 useslatchkey-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.