Stale bot FAQ
The stale bot is an automated tool that monitors GitHub issues and pull requests and closes them if they have been inactive for a certain period of time. The bot helps to keep the issue tracker clean and relevant by removing outdated or irrelevant issues.
The stale bot is installed to help keep the issue tracker clean and relevant. Issues that have not been updated for a long period of time may no longer be relevant or actionable, so the bot helps to ensure that the issue tracker is not cluttered with old or outdated issues.
Even then, a good proportion of tickets reach a point where a year has passed without activity, the stale bot will then start processing it.
Yes, you can prevent your issue from being closed by the stale bot by keeping it updated with relevant information or by adding a comment to indicate that the issue is still relevant. This will reset the inactivity timer and prevent the bot from closing the issue.
Your bug or feature request may have been closed by the stale bot if it had been inactive for a certain period of time. The bot is designed to keep the issue tracker clean and relevant, so if an issue has not been updated for a long period of time, it may be closed by the bot.
The stale bot does not determine whether an issue is valid or not. The bot simply closes issues that have been inactive for a certain period of time in order to keep the issue tracker clean and relevant. If you believe that your issue is still valid and relevant, you can prevent it from being closed by updating it with relevant information or adding a comment to indicate that the issue is still relevant.
The arguments against stale bots centre on stale bots locking issues and preventing further discussion. Our stale bot does not lock issues. Ultimately, it's our project, we will run it the way we wish to run it. You are welcome to run a clone of this project without a stale bot.