Mark stale issues and pull requests workflow (remy/nodemon)
The Mark stale issues and pull requests workflow from remy/nodemon, 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 stale issues and pull requests workflow from the remy/nodemon 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 stale issues and pull requests
on:
schedule:
- cron: "0 * * * *"
jobs:
stale:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@v3
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-stale: 14
days-before-close: 30
days-before-pr-close: -1
stale-issue-label: 'stale'
stale-pr-label: 'stale'
stale-issue-message: >
This issue has been automatically marked as idle and stale because it hasn't
had any recent activity. It will be automtically closed if no further activity
occurs. If you think this is wrong, or the problem still persists, just pop
a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3
close-issue-message: 'Automatically closing this issue due to lack of activity'
exempt-issue-labels: not-stale,security,pinned
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 * * * *" jobs: stale: timeout-minutes: 30 runs-on: latchkey-small permissions: issues: write pull-requests: write steps: - uses: actions/stale@v3 with: repo-token: ${{ secrets.GITHUB_TOKEN }} days-before-stale: 14 days-before-close: 30 days-before-pr-close: -1 stale-issue-label: 'stale' stale-pr-label: 'stale' stale-issue-message: > This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up. Thank you for contributing <3 close-issue-message: 'Automatically closing this issue due to lack of activity' exempt-issue-labels: not-stale,security,pinned
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.