-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add workflows to auto-close and lock stale issues and PRs #2335
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I misunderstood the API :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Minor nits, but even those are questionable, so feel free to merge as-is.
If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. | ||
issue-inactive-days: 30 | ||
pr-comment: > | ||
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Still references issues here (and in the following line). Maybe change it to use 'pull requests' instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That being said, I wonder if opening issues still makes more sense than open a new pull request. Feel free to ignore.
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When I was adding the
bug/has-workaround
label to tickets yesterday, I noticed there are a handful of issues labeledwaiting-on-answer
where we haven't heard back from the user in months. I figured we should automate posting a "warning" and then closing the issue after a set amount of time. I also added a workflow that locks threads after 30 days to encourage folks to create new issues rather than replying to old closed issues forever. Kudos to the Editor Experience team for giving me a template to work from!Closes #683