stale_issue.yml

name: "Close stale issues"

# Controls when the action will run.
on:
  schedule:
  - cron: "0 0 * * *"

permissions:
  contents: read

jobs:
  issue-cleanup:
    permissions:
      issues: write
      contents: read
      pull-requests: write
    runs-on: ubuntu-latest
    name: Stale issue job
    steps:
    - uses: aws-actions/stale-issue-cleanup@2017b87caa8e25014362d434a980d60fa758f3af
      with:
        issue-types: issues
        stale-issue-message: Greetings! It looks like this issue hasn’t been 
          active in longer than five days. We encourage you to check if this is still an issue in the latest release. 
          In the absence of more information, we will be closing this issue soon. 
          If you find that this is still a problem, please feel free to provide a comment or upvote 
          with a reaction on the initial post to prevent automatic closure. If the issue is already closed, 
          please feel free to open a new one.
        # These labels are required
        stale-issue-label: closing-soon
        exempt-issue-labels: automation-exempt,needs-review
        response-requested-label: response-requested

        # Don't set closed-for-staleness label to skip closing very old issues
        # regardless of label
        closed-for-staleness-label: closed-for-staleness

        # Issue timing
        days-before-stale: 10
        days-before-close: 4

        # If you don't want to mark a issue as being ancient based on a
        # threshold of "upvotes", you can set this here. An "upvote" is
        # the total number of +1, heart, hooray, and rocket reactions
        # on an issue.
        minimum-upvotes-to-exempt: 2

        repo-token: ${{ secrets.GITHUB_TOKEN }}
        loglevel: DEBUG