-
Notifications
You must be signed in to change notification settings - Fork 371
Apply labels and close stale issues and PRs #5111
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
base: master
Are you sure you want to change the base?
Apply labels and close stale issues and PRs #5111
Conversation
|
This makes sense to me, but I'd like @ahnitz 's approval as well before merging. |
|
I generally dislike this approach to issues, but will not oppose if there is consensus from others. |
|
I think this is fine. The main issue is making sure people then add long-term labels to planning things and 'bug' as appropriate. |
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.
Pull Request Overview
This PR implements a GitHub workflow to automatically mark stale issues and PRs, reducing backlog by closing those inactive for 60 days.
- Adds a new GitHub action workflow using actions/stale@v9.
- Configures exempt labels ("bug" and "long term") to prevent auto-closure of important items.
|
I do see this as more a reminder to close if things are transient, or a kick to get things moving if it has just been delayed Please approve or reject if we don't want this |
|
Ping on this |
This implements a new GitHub action to apply labels warning that a PR or issue is stale, and closes it automatically if nothing happens for a week after it has been labelled stale
I think I've set it so that we can apply
bugorlong termlabels so that this won't happen.Standard information about the request
This is a new feature for GitHub management
This change has been proposed using the contribution guidelines
Motivation
I want to reduce the number of issues, and this is the easiest way to do that, rather than commenting on each one asking for an update.
Contents
Add a GitHub workflow which uses the Close Stale Issues action to mark and close issues/PRs
Links to any issues or associated PRs
I could link all the issues and PRs older than a couple of months, but lets not do that for now.
Testing performed
None