Close Stale Issues workflow (modelscope/twinkle)

The Close Stale Issues workflow from modelscope/twinkle, 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.

Grade your own workflow free or run it on Latchkey →

Source: modelscope/twinkle.github/workflows/close_tale_issue.yamlLicense Apache-2.0View source

What it does

This is the Close Stale Issues workflow from the modelscope/twinkle 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 Issues
on:
  schedule:
    - cron: '0 0 * * *'
  workflow_dispatch:

jobs:
  close-stale:
    runs-on: ubuntu-latest
    steps:
      - name: Close stale issues
        uses: actions/stale@v8
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          days-before-stale: 90
          days-before-close: 7
          stale-issue-message: 'This issue has been inactive for over 3 months and will be automatically closed in 7 days. If this issue is still relevant, please reply to this message.'
          close-issue-message: 'This issue has been automatically closed due to inactivity. If needed, it can be reopened.'
          stale-issue-label: 'stale'
          exempt-all-issue-labels: true

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 0 * * *'
  workflow_dispatch:
 
jobs:
  close-stale:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Close stale issues
        uses: actions/stale@v8
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          days-before-stale: 90
          days-before-close: 7
          stale-issue-message: 'This issue has been inactive for over 3 months and will be automatically closed in 7 days. If this issue is still relevant, please reply to this message.'
          close-issue-message: 'This issue has been automatically closed due to inactivity. If needed, it can be reopened.'
          stale-issue-label: 'stale'
          exempt-all-issue-labels: true

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

actions/stale