You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
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: writepull-requests: writejobs:
stale:
runs-on: ubuntu-lateststeps:
- uses: actions/stale@v8with:
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: 30days-before-close: 5days-before-pr-close: -1# Never close a PR
The text was updated successfully, but these errors were encountered:
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.
It might be worth including a stale issues bot, we could use the stale action
something like
.github/workflows/stale.yml
:The text was updated successfully, but these errors were encountered: