Close Stale Issues workflow (ipfs-shipyard/py-ipfs)

The Close Stale Issues workflow from ipfs-shipyard/py-ipfs, explained and optimized by Latchkey.

What it does

This is the Close Stale Issues workflow from the ipfs-shipyard/py-ipfs 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

name: Close Stale Issues

on:
  schedule:
    - cron: '0 0 * * *'
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

jobs:
  stale:
    uses: ipdxco/unified-github-workflows/.github/workflows/reusable-stale-issue.yml@v1

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:
 
permissions:
  issues: write
  pull-requests: write
 
jobs:
  stale:
    timeout-minutes: 30
    uses: ipdxco/unified-github-workflows/.github/workflows/reusable-stale-issue.yml@v1
 

What changed

• 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.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.