Mark stale issues and pull requests workflow (jquery-validation/jquery-validation)
The Mark stale issues and pull requests workflow from jquery-validation/jquery-validation, 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 jquery-validation/jquery-validation 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
# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
#
# You can adjust the behavior by modifying this file.
# For more information, see:
# https://github.com/actions/stale
name: Mark stale issues and pull requests
on:
schedule:
- cron: '10 05 * * *'
jobs:
stale:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@v5
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: >
This issue lacks verification. Please provide a reproduction link.
Thank you for contributing :)
stale-pr-message: >
This issue/proposal has been automatically marked as idle and stale because it hasn't
had any recent activity. It will be automatically 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 one of the maintainers will (try!) to follow up.
Thank you for contributing :)
stale-issue-label: 'stale'
stale-pr-label: 'stale'
exempt-all-milestones: true
exempt-issue-labels: 'Status: Verified, Type: Feature'
exempt-pr-labels: 'MERGE ME, NEEDS REVIEW'
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time. # # You can adjust the behavior by modifying this file. # For more information, see: # https://github.com/actions/stale name: Mark stale issues and pull requests on: schedule: - cron: '10 05 * * *' jobs: stale: timeout-minutes: 30 runs-on: latchkey-small permissions: issues: write pull-requests: write steps: - uses: actions/stale@v5 with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: > This issue lacks verification. Please provide a reproduction link. Thank you for contributing :) stale-pr-message: > This issue/proposal has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automatically 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 one of the maintainers will (try!) to follow up. Thank you for contributing :) stale-issue-label: 'stale' stale-pr-label: 'stale' exempt-all-milestones: true exempt-issue-labels: 'Status: Verified, Type: Feature' exempt-pr-labels: 'MERGE ME, NEEDS REVIEW'
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.