Creates the config file for stalebot to help us clean up old/inactive issues #2441
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
imwiss
approved these changes
May 10, 2022
| limitPerRun: 30 | ||
|
|
||
| # Limit to only `issues` or `pulls` | ||
| only: issues |
There was a problem hiding this comment.
Would it be worth adding pulls here, too?
There was a problem hiding this comment.
I'd like to parse through the pulls a bit more given that folks put in the extra effort to make the changeset and I'd like to validate if the changes are still relevant before something beneficial gets closed.
nickfloyd
added
Type: Maintenance
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.
We are in need of some house cleaning to get us back to a good "supported" state. This will activate the stalebot to help us parse through any issues that are either no longer relevant, need to be rethought, or are not able to be addressed.
Note: It's not that these issues are not important or useful. We simply need a clear starting point to begin actively introducing improvements and changes into this SDK. If anyone feels like the issues that are marked as stale from the bot still need to be opened they can label them with the
pinnedandfollowup-neededlabels with some details on the current state of things so that it will not auto close. That way we can have a closer look at the issue and see what we need to do to get it resolved.