feat: Add workflow to automatically close stale issues #692
Conversation
This file contains hidden or 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
2 participants
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.
Related: #681
Purpose of the pull request
This PR adds an automated workflow to help maintain our issue tracker by closing issues that have been waiting for user feedback but haven't received any response. When maintainers are waiting for additional information from issue reporters, they can apply the
waiting for feedbacklabel. If the issue remains inactive for 30 days, the workflow will add astalelabel and post a warning. If there's still no response after another 7 days, it automatically closes the issue with a message letting the user know they can reopen it if needed.What's changed?
A new GitHub Actions workflow file
issue-close-stale.ymlhas been added that runs daily to check for inactive issues.Checklist