Add workflow to mark issues and PRs as stale #724
Merged
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
|
30 days wouldn't hurt tbh, would also probably be a good indicator since that's two "sprints" w/o any activity? |
I think that's not a bad idea for PRs because you shouldn't be idle on a PR for more than a month. Issues aren't necessarily stale after 30 days if no one's gotten to them, though. We don't move that quickly. |
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.
Summary
With this workflow, if an issue or PR has had no activity for 60 days, it will be marked as stale, which is basically a reminder for us to look at it again so nothing gets forgotten. It's 60 days because that's the default, if anyone has a compelling reason to change that I'd be down.
Test Plan
Just wait for it to mark something as stale 🤷♂️