stale.yml

name: Stale Issues and PRs
on:
  schedule:
  # Process new stale issues once a day. Folks can /fresh for a fast un-stale
  # per the commands workflow. Run at 1:15 mostly as a somewhat unique time to
  # help correlate any issues with this workflow.
  - cron: '15 1 * * *'
  workflow_dispatch: {}

permissions:
  issues: write
  pull-requests: write

jobs:
  stale:
    runs-on: ubuntu-22.04
    steps:
    - uses: actions/stale@1160a2240286f5da8ec72b1c0816ce2481aabf84 # v8
      with:
        # This action uses ~2 operations per stale issue per run to determine
        # whether it's still stale. It also uses 2-3 operations to mark an issue
        # stale or not. During steady state (no issues to mark stale, check, or
        # close) we seem to use less than 10 operations with ~150 issues and PRs
        # open.
        #
        # Our hourly rate-limit budget for all workflows that use GITHUB_TOKEN
        # is 1,000 requests per the below docs.
        # https://docs.github.com/en/rest/overview/resources-in-the-rest-api#requests-from-github-actions
        operations-per-run: 100
        days-before-stale: 90
        days-before-close: 14
        stale-issue-label: stale
        exempt-issue-labels: exempt-from-stale
        stale-issue-message: >
          Crossplane does not currently have enough maintainers to address every
          issue and pull request. This issue has been automatically marked as
          `stale` because it has had no activity in the last 90 days. It will be
          closed in 14 days if no further activity occurs. Leaving a comment
          **starting with** `/fresh` will mark this issue as not stale.
        stale-pr-label: stale
        exempt-pr-labels: exempt-from-stale
        stale-pr-message:
          Crossplane does not currently have enough maintainers to address every
          issue and pull request. This pull request has been automatically
          marked as `stale` because it has had no activity in the last 90 days.
          It will be closed in 14 days if no further activity occurs.
          Adding a comment **starting with** `/fresh` will mark this PR as not stale.