Mark stale issues and pull requests workflow (http-party/http-server)

The Mark stale issues and pull requests workflow from http-party/http-server, explained and optimized by Latchkey.

What it does

This is the Mark stale issues and pull requests workflow from the http-party/http-server 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: '25 12 * * *'

jobs:
  stale:

    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write

    steps:
    - uses: actions/stale@v4.0.0
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        days-before-stale: 360
        days-before-issue-stale: 180
        days-before-pr-stale: 360
        stale-issue-message: 'This issue has been inactive for 180 days'
        stale-pr-message: 'This pull request has been inactive for 360 days'
        stale-issue-label: 'stale'
        stale-pr-label: 'stale'
        exempt-issue-labels: 'no-stale'
        exempt-pr-labels: 'no-stale'
        exempt-all-milestones: true
        days-before-close: -1

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: '25 12 * * *'
 
jobs:
  stale:
    timeout-minutes: 30
 
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: write
 
    steps:
    - uses: actions/stale@v4.0.0
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        days-before-stale: 360
        days-before-issue-stale: 180
        days-before-pr-stale: 360
        stale-issue-message: 'This issue has been inactive for 180 days'
        stale-pr-message: 'This pull request has been inactive for 360 days'
        stale-issue-label: 'stale'
        stale-pr-label: 'stale'
        exempt-issue-labels: 'no-stale'
        exempt-pr-labels: 'no-stale'
        exempt-all-milestones: true
        days-before-close: -1
 

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 uses latchkey-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.

Actions used in this workflow