GitHub Action to close issues as stale as-needed #360
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
dbeatty10
requested review from
graciegoheen,
dave-connors-3 and
b-per
as code owners
graciegoheen
approved these changes
Jul 19, 2023
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.
Description & motivation
What?
For issues that have been open for awhile without activity, label
them as stale with a warning that they will be closed out. If
anyone comments to keep the issue open, it will automatically
remove the stale label and keep it open.
Stale label rules:
awaiting_response,more_information_needed-> 90 daysgood_first_issue,help_wanted-> 360 days (a year)tech_debt-> 720 (2 years)Why?
To keep the repo in a clean state from issues that aren't relevant anymore
When?
Once a day