Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Stale issue bot #40

Open
scagood opened this issue Jul 7, 2023 · 2 comments
Open

Stale issue bot #40

scagood opened this issue Jul 7, 2023 · 2 comments

Comments

@scagood
Copy link
Contributor

scagood commented Jul 7, 2023

It might be worth including a stale issues bot, we could use the stale action

something like .github/workflows/stale.yml:

name: 'Close stale issues'
on:
  schedule:
    - cron: '30 1 * * *'

permissions:
  issues: write
  pull-requests: write

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v8
        with:
          stale-issue-message: 'This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.'
          close-issue-message: 'This issue was closed because it has been stalled for 30 days with no activity.'
          days-before-stale: 30
          days-before-close: 5
          days-before-pr-close: -1 # Never close a PR
@savetheclocktower
Copy link
Member

I think it's fine to close an issue if we need more information from the reporter and never get it, but if it's just something that we haven't gotten around to yet, then I'd want it to stay open. If there's any way to capture that nuance with a bot, then I'd be OK with it.

@scagood
Copy link
Contributor Author

scagood commented Jul 7, 2023

There are exempt-issue-labels

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants