Close inactive issues workflow (derisk-ai/OpenDerisk)

The Close inactive issues workflow from derisk-ai/OpenDerisk, 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: derisk-ai/OpenDerisk.github/workflows/close-issue.ymlLicense MITView source

What it does

This is the Close inactive issues workflow from the derisk-ai/OpenDerisk 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: "00 21 * * *"

jobs:
  close-issues:
    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write
    steps:
      - uses: actions/stale@v5
        with:
          days-before-issue-stale: 120
          days-before-issue-close: 90 
          stale-issue-label: "stale"
          stale-issue-message: "This issue has been marked as `stale`, because it has been over 30 days without any activity."
          close-issue-message: "This issue bas been closed, because it has been marked as `stale` and there has been no activity for over 7 days."
          days-before-pr-stale: -1
          days-before-pr-close: -1
          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: "00 21 * * *"
 
jobs:
  close-issues:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: write
    steps:
      - uses: actions/stale@v5
        with:
          days-before-issue-stale: 120
          days-before-issue-close: 90 
          stale-issue-label: "stale"
          stale-issue-message: "This issue has been marked as `stale`, because it has been over 30 days without any activity."
          close-issue-message: "This issue bas been closed, because it has been marked as `stale` and there has been no activity for over 7 days."
          days-before-pr-stale: -1
          days-before-pr-close: -1
          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 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