chore: remove no-response workflow
#158
Conversation
Having too many open issues is not a problem in this repository. It can easily be dealt with manually and as such be judged in a much more productive manner, avoiding needless closing / opening / closing as in eg #33 This PR essentially reverts #3 I would like to remove this from the rest of the eslint-community repositories as well, until we see a need.
|
It's fine to delete For example, narrow down auto closed issues and PRs to those with labels that require updates, such as with:
+ any-of-labels: 'needs repro,needs info,needs update' |
|
@ota-meshi I would love for us to do that once we see that it becomes a problem for us to manage manually A personal response is much less hostile than an automatic one. I myself gets extremely discouraged when a bot blindly closes my issues + it creates a lot of needless noise. That said, I'm open to that for some of the others, any one in particular that you have in mind? |
|
🎉 This PR is included in version 4.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Having too many open issues is not a problem in this repository. It can easily be dealt with manually and as such be judged in a much more productive manner, avoiding needless closing / opening / closing as in eg #33
This PR essentially reverts #3.
I would like to remove this from the rest of the
eslint-communityrepositories as well, until we see a need for it in a repository.