Skip to content

Conversation

@Mr0grog
Copy link
Member

@Mr0grog Mr0grog commented Oct 17, 2025

Long ago, we added the stale issue bot to help manage the influx of a lot of ideas and brainstorming against a small implementation team. Today, the web-monitoring tools mostly just have one maintainer (me) and are not flooded with a lot of issues and ideas. Long-lived issues are more common, and they are helpful for me to keep track of things over the slow pace and timeframe in which I can individually address stuff. Stale bot feels like it is getting more in the way than helping in the current moment, so I’m disabling it. (Also, it’s deprecated! Where we need it, we should switch to the action, which is the currently supported approach.)

Context: Stale bot seems to have been dead for a while (I actually thought we’d disabled it), but it seems to have woken up today and marked a huge pile of issues as stale across a whole lot of repos.

Long ago, we added the stale issue bot to help manage the influx of a lot of ideas and brainstorming against a small implementation team. Today, the web-monitoring tools mostly just have one maintainer (me) and are not flooded with a lot of issues and ideas. Long-lived issues are more common, and they are helpful for me to keep track of things over the slow pace and timeframe in which I can individually address stuff. Stale bot feels like it is getting more in the way than helping in the current moment, so I’m disabling it.
@Mr0grog Mr0grog merged commit e707d1c into main Oct 17, 2025
6 checks passed
@Mr0grog Mr0grog deleted the stalebot-is-stale branch October 17, 2025 16:26
@github-project-automation github-project-automation bot moved this from Inbox to Done in Web Monitoring Oct 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants