feat: Use GitHub actions for Stale detection #3001
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
hay-kot
reviewed
Jan 17, 2024
hay-kot
approved these changes
Jan 17, 2024
|
only thing im not sure on here is whether 30 (+5) days for issues are enough to close them automatically. |
Kuchenpirat
approved these changes
Jan 17, 2024
|
Thanks for the comments guys. Definitely happy to review the 30+5, I'm not wedded to any particular value. Main focus with this initial PR was to get it implemented and see how it functions in dry run mode. |
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.
What type of PR is this?
What this PR does / why we need it:
We haven't had stalebot working for a while. This implementation gets rid of the old stale config, and introduces the official GitHub Action for stale issues/PRs: https://github.com/marketplace/actions/close-stale-issues
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
You'll note debug mode is turned on - this means that it should take no action against anything until we remove that flag. Relevant doco
I'll monitor what I can see in the Actions output as time allows, and raise a new PR in the next week or so to remove the flag, including any tweaks that seem worthwhile.
Also TBC whether there'd be permissions issues, but I think we fix forward with that once we see how it wants to act.
Testing
Very little, per the special notes, the plan would be to implement this effectively dormant, and then tweak config as needed based on what we see "in production".