Stale issues workflow #2322
Merged
Stale issues workflow #2322
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on Slack, this adds a Github bot to deal with stale issues. Unlike what I said on Slack this version does not seem to be able to exclude issues created by members, but only by labels. I would argue that's actually not a bad thing.
Currently it will run once every day. It will exclude issues labelled with: Bug,Blocked,Blocker,Design,enhancement
so we have to make sure that we apply any of those if we wish to avoid being reminded on an issues going stale.
There is a rate limit of 30 issues per day it can close (something todo with github APIs). This means it will initially take a couple of days to go through all open issues once merged.