-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Close issues #774
Comments
👍 |
Okay I'll have a go. Might take a few days. |
@Nebucatnetzer what is the current status of this? |
#236 is over two years old and the author hasn't answered since over a year. As a note to the issues listed here. I personally would close old stuff from time to time to keep things in order. |
Thanks for the list! |
You can implement something like probot/stale to do this automatically and also remind that you have stale issues :) |
Aye that would work as well but it is up to the devs to decide if they want to automate this. |
Closing this. 😉 All the mentioned issues have been dealt with long ago. Any further needed "meta" discussions about repo management can go into new issue(s) or other channels. |
There are a lot of open issues which should get closed IMO.
Keeping them open gives the impression that the repo isn't properly maintained.
If it helps I can compile a list of all rhe issues that should get closed im my opinion.
The text was updated successfully, but these errors were encountered: