Close stale issue workflow (intel/neural-compressor)
The Close stale issue workflow from intel/neural-compressor, 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 stale issue workflow from the intel/neural-compressor 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
workflow (.yml)
name: Close stale issue
permissions:
contents: read
issues: write
on:
schedule:
- cron: "30 22 * * *"
workflow_dispatch:
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v10
with:
start-date: '2020-01-01T00:00:00Z'
days-before-issue-stale: 60
days-before-issue-close: 7
stale-issue-message: "This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days."
close-issue-message: "This issue was closed because it has been stalled for 7 days with no activity."
operations-per-run: 500
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Close stale issue permissions: contents: read issues: write on: schedule: - cron: "30 22 * * *" workflow_dispatch: jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/stale@v10 with: start-date: '2020-01-01T00:00:00Z' days-before-issue-stale: 60 days-before-issue-close: 7 stale-issue-message: "This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days." close-issue-message: "This issue was closed because it has been stalled for 7 days with no activity." operations-per-run: 500
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.