Close Stale Issues workflow (Crosstalk-Solutions/unifi-toolkit)
The Close Stale Issues workflow from Crosstalk-Solutions/unifi-toolkit, 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.
What it does
This is the Close Stale Issues workflow from the Crosstalk-Solutions/unifi-toolkit 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: Close Stale Issues
on:
schedule:
- cron: '0 9 * * *' # Daily at 9:00 UTC
workflow_dispatch: # Allow manual trigger
permissions:
issues: write
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v10
with:
days-before-stale: 7
days-before-close: 7
stale-issue-label: stale
stale-issue-message: >
This issue has been automatically marked as stale because it has not
had activity in 7 days. It will be closed in 7 days if no further
activity occurs. If this is still relevant, please leave a comment.
close-issue-message: >
This issue has been automatically closed due to inactivity. If the
problem persists, feel free to reopen or file a new issue.
only-issue-labels: ''
only-pr-labels: ''
days-before-pr-stale: -1
days-before-pr-close: -1
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Close Stale Issues on: schedule: - cron: '0 9 * * *' # Daily at 9:00 UTC workflow_dispatch: # Allow manual trigger permissions: issues: write jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/stale@v10 with: days-before-stale: 7 days-before-close: 7 stale-issue-label: stale stale-issue-message: > This issue has been automatically marked as stale because it has not had activity in 7 days. It will be closed in 7 days if no further activity occurs. If this is still relevant, please leave a comment. close-issue-message: > This issue has been automatically closed due to inactivity. If the problem persists, feel free to reopen or file a new issue. only-issue-labels: '' only-pr-labels: '' days-before-pr-stale: -1 days-before-pr-close: -1
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.