Auto Close Stale Discussions workflow (prisma/prisma)

The Auto Close Stale Discussions workflow from prisma/prisma, explained and optimized by Latchkey.

What it does

This is the Auto Close Stale Discussions workflow from the prisma/prisma 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

name: Auto Close Stale Discussions

on:
  schedule:
    - cron: '0 0 * * *' # Runs daily at midnight UTC
  workflow_dispatch: # Enables manual run from the Actions tab

permissions:
  contents: read
  discussions: write

jobs:
  close-discussions:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6

      - name: Setup PNPM
        uses: pnpm/action-setup@v4
        with:
          run_install: false

      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: '20.19.0'
          cache: 'pnpm'

      - name: Install dependencies
        run: pnpm install

      - name: Run inline Discussion Cleanup Script
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CLOSING_MESSAGE: |
            Hi,

            As we have not heard back from you, we are closing this discussion to keep our discussions organized.

            Feel free to start a new discussion if this remains relevant.

            Thank you for being part of the community!
        run: node ./.github/workflows/scripts/auto-close-github-discussions.js

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Auto Close Stale Discussions
 
on:
  schedule:
    - cron: '0 0 * * *' # Runs daily at midnight UTC
  workflow_dispatch: # Enables manual run from the Actions tab
 
permissions:
  contents: read
  discussions: write
 
jobs:
  close-discussions:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
 
      - name: Setup PNPM
        uses: pnpm/action-setup@v4
        with:
          run_install: false
 
      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: '20.19.0'
          cache: 'pnpm'
 
      - name: Install dependencies
        run: pnpm install
 
      - name: Run inline Discussion Cleanup Script
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CLOSING_MESSAGE: |
            Hi,
 
            As we have not heard back from you, we are closing this discussion to keep our discussions organized.
 
            Feel free to start a new discussion if this remains relevant.
 
            Thank you for being part of the community!
        run: node ./.github/workflows/scripts/auto-close-github-discussions.js
 

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.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

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