Mark stale issues and pull requests workflow (PINTO0309/onnx2tf)

The Mark stale issues and pull requests workflow from PINTO0309/onnx2tf, 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: PINTO0309/onnx2tf.github/workflows/stale.ymlLicense MITView source

What it does

This is the Mark stale issues and pull requests workflow from the PINTO0309/onnx2tf 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)

# 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 9 * * *'

jobs:
  stale:

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

    steps:
    - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'If there is no activity within the next two days, this issue will be closed automatically.'
        stale-pr-message: 'If there is no activity within the next two days, this pr will be closed automatically.'
        stale-issue-label: 'no-issue-activity'
        stale-pr-label: 'no-pr-activity'
        exempt-issue-labels: TODO,discussion,Bug,feature request
        exempt-pr-labels: TODO,discussion,Bug,feature request
        days-before-stale: 5
        days-before-close: 1

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 9 * * *'
 
jobs:
  stale:
    timeout-minutes: 30
 
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: write
 
    steps:
    - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'If there is no activity within the next two days, this issue will be closed automatically.'
        stale-pr-message: 'If there is no activity within the next two days, this pr will be closed automatically.'
        stale-issue-label: 'no-issue-activity'
        stale-pr-label: 'no-pr-activity'
        exempt-issue-labels: TODO,discussion,Bug,feature request
        exempt-pr-labels: TODO,discussion,Bug,feature request
        days-before-stale: 5
        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

actions/stale