Mark stale issues and pull requests workflow (PaddlePaddle/PaddleRS)

The Mark stale issues and pull requests workflow from PaddlePaddle/PaddleRS, 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.

Grade your own workflow free or run it on Latchkey →

Source: PaddlePaddle/PaddleRS.github/workflows/stale.ymlLicense Apache-2.0View source

What it does

This is the Mark stale issues and pull requests workflow from the PaddlePaddle/PaddleRS repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

# 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: '0 17 * * *'

jobs:
  stale:

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

    steps:
    - uses: actions/stale@v5
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.'
        stale-issue-label: 'stale'
        close-issue-reason: 'completed'
        exempt-issue-labels: 'bug, dependencies, documentation, enhancement, WIP'
        operations-per-run: 900
        days-before-pr-stale: -1
        days-before-pr-close: -1
        ascending: true

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: '0 17 * * *'
 
jobs:
  stale:
    timeout-minutes: 30
 
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: none
 
    steps:
    - uses: actions/stale@v5
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.'
        stale-issue-label: 'stale'
        close-issue-reason: 'completed'
        exempt-issue-labels: 'bug, dependencies, documentation, enhancement, WIP'
        operations-per-run: 900
        days-before-pr-stale: -1
        days-before-pr-close: -1
        ascending: true

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

actions/stale