Mark stale issues and pull requests workflow (clusterzx/paperless-ai)
The Mark stale issues and pull requests workflow from clusterzx/paperless-ai, 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.
What it does
This is the Mark stale issues and pull requests workflow from the clusterzx/paperless-ai 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: Mark stale issues and pull requests
on:
schedule:
- cron: "0 0 * * *" # Runs daily at midnight
jobs:
stale:
runs-on: ubuntu-latest
steps:
- name: Close stale issues and pull requests
uses: actions/stale@v8
with:
repo-token: ${{ secrets.stale_bot }}
stale-issue-message: "This issue has been marked as stale due to inactivity. Please respond to keep it open."
stale-pr-message: "This pull request has been marked as stale due to inactivity. Please update it to keep it open."
close-issue-message: "This issue has been closed due to lack of response."
close-pr-message: "This pull request has been closed due to lack of response."
days-before-stale: 7 # Days before an issue or PR is marked as stale
days-before-close: 3 # Days before a stale issue or PR is closed
stale-issue-label: "stale" # Label added to stale issues
exempt-issue-labels: "wontfix,bug" # Labels that exempt issues from being marked as stale
only-issues: true # Only affect issues, not PRs
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Mark stale issues and pull requests on: schedule: - cron: "0 0 * * *" # Runs daily at midnight jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Close stale issues and pull requests uses: actions/stale@v8 with: repo-token: ${{ secrets.stale_bot }} stale-issue-message: "This issue has been marked as stale due to inactivity. Please respond to keep it open." stale-pr-message: "This pull request has been marked as stale due to inactivity. Please update it to keep it open." close-issue-message: "This issue has been closed due to lack of response." close-pr-message: "This pull request has been closed due to lack of response." days-before-stale: 7 # Days before an issue or PR is marked as stale days-before-close: 3 # Days before a stale issue or PR is closed stale-issue-label: "stale" # Label added to stale issues exempt-issue-labels: "wontfix,bug" # Labels that exempt issues from being marked as stale only-issues: true # Only affect issues, not PRs
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.