Mark and close stale issues workflow (parallax/jsPDF)
The Mark and close stale issues workflow from parallax/jsPDF, explained and optimized by Latchkey.
A
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 and close stale issues workflow from the parallax/jsPDF 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: Mark and close stale issues
on:
schedule:
- cron: "30 1 * * *"
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v10
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: 'This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.'
stale-issue-label: 'no-issue-activity'
exempt-issue-labels: 'Bug,Feature Request,persistent'
remove-stale-when-updated: true
days-before-stale: 90
days-before-close: 7
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Mark and close stale issues on: schedule: - cron: "30 1 * * *" jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/stale@v10 with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: 'This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.' stale-issue-label: 'no-issue-activity' exempt-issue-labels: 'Bug,Feature Request,persistent' remove-stale-when-updated: true days-before-stale: 90 days-before-close: 7
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.