Mark stale issues and pull requests workflow (Kristories/awesome-guidelines)
The Mark stale issues and pull requests workflow from Kristories/awesome-guidelines, 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 Kristories/awesome-guidelines repository, a real project running GitHub Actions. It is shown here with attribution under its CC0-1.0 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: "59 23 * * *"
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v1
with:
days-before-stale: 20
days-before-close: 1
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: 'This issue has been hanging around a bit too long, if needed please update or comment.'
stale-pr-message: 'This PR has been hanging around a bit too long, please update/rebase or comment as needed.'
stale-issue-label: 'no-issue-activity'
stale-pr-label: 'no-pr-activity'
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: "59 23 * * *" jobs: stale: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/stale@v1 with: days-before-stale: 20 days-before-close: 1 repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: 'This issue has been hanging around a bit too long, if needed please update or comment.' stale-pr-message: 'This PR has been hanging around a bit too long, please update/rebase or comment as needed.' stale-issue-label: 'no-issue-activity' stale-pr-label: 'no-pr-activity'
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.