coveralls
commented
10 months ago coverage: 74.831%. remained the same when pulling f2d66f37dcbccf4a24ffa3c0b3edfb9361e9b18f on jav/cleanup-inactive into 57d2672fad614e374a61f228e6ff6130e10b8d7f on master.
Description
FYI, Zappa turns 8 years old on January 20th! 🎂
Unfortunately, that also means we have a lot of Issues/PRs migrated from the original repo that are nearly that old too. As a result, we currently have an unwieldy mess of a backlog that makes it difficult to properly prioritize and evaluate Issues/PRs and whether they still are relevant after, in many cases, several years of new Zappa releases. Manually triaging this kind of historical backlog would take up a lot of time and result in few actionable items.
So, in the interest of reducing both the maintenance load and clutter in this repo, this PR adds a bot that will identify Issues/PRs that haven't seen any activity in at least 90 days (~3 months), and will leave a comment to inform the author (and/or any other interested users) that they can add a comment within 10 days to keep the Issue/PR open (and, if they do so, the bot will label it as needing attention from Zappa's maintainers).
However, if no comment is added within 10 days (which I imagine will be the case for the vast majority of our multi-year old Issues/PRs), then the bot will automatically close it to reduce clutter (while again leaving a helpful comment for users who may find the closed Issue/PR in the future that instructs them to open a new Issue/PR if they find it's still relevant).
Note: This PR introduces this bot in "dry-run"/"debug mode", which means it won't actually make any changes, but will log what changes it would have made. Letting it go through a few dry-runs first will provide us with data that will show us if it is behaving as intended. If not, the config can be tweaked, but, if so, "debug mode" can be turned off so this bot can begin helping us create a more organized repo with a more manageable backlog for 2024. 🎉