Close inactive issues workflow (Acode-Foundation/Acode)
The Close inactive issues workflow from Acode-Foundation/Acode, 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 Close inactive issues workflow from the Acode-Foundation/Acode 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: Close inactive issues
on:
schedule:
- cron: "30 1 * * *"
jobs:
close-issues:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@v10
with:
days-before-issue-stale: 60
days-before-issue-close: 14
stale-issue-label: "stale"
stale-issue-message: >
Hi there! 👋
We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Acode, please let us know by commenting on this issue(i.e Bump!), and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 14 days.
Thanks for your help!
close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
exempt-all-milestones: true
days-before-pr-stale: -1
days-before-pr-close: -1
exempt-issue-labels: "new plugin idea, todo, enhancement, bug, Low priority, documentation"
operations-per-run: 100
repo-token: ${{ secrets.GITHUB_TOKEN }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Close inactive issues on: schedule: - cron: "30 1 * * *" jobs: close-issues: timeout-minutes: 30 runs-on: latchkey-small permissions: issues: write pull-requests: write steps: - uses: actions/stale@v10 with: days-before-issue-stale: 60 days-before-issue-close: 14 stale-issue-label: "stale" stale-issue-message: > Hi there! 👋 We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Acode, please let us know by commenting on this issue(i.e Bump!), and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 14 days. Thanks for your help! close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale." exempt-all-milestones: true days-before-pr-stale: -1 days-before-pr-close: -1 exempt-issue-labels: "new plugin idea, todo, enhancement, bug, Low priority, documentation" operations-per-run: 100 repo-token: ${{ secrets.GITHUB_TOKEN }}
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.