nest
nest copied to clipboard
nestjs
Do not lock closed issues on GitHub
Is there an existing issue that is already proposing this?
- [X] I have searched the existing issues
Is your feature request related to a problem? Please describe it
When we have problems, we searches inside the issues if someone already notified it. But when it is the case, most of the time the issues are old (ok), closed (ok), and locked (doh!!!), which prevents us from being able to ask for additional information, or to complete the issue by possible workarounds, particularly when no workaround is given or not enough clearly.
Describe the solution you'd like
Do not lock closed issues.
Teachability, documentation, adoption, migration strategy
None.
What is the motivation / use case for changing the behavior?
It would be more practical to let the possibility to add new comments on the closed issues, even several years later, just to complete the discussion, ask for additional information, and propose new workarounds for the next readers having the same problem. It happens often to me, and it's very frustrating to see the issues closed without concrete workaround given. And when I find one, I would like to share it to give a solution to the next readers like me. Plus, it avoids the creation of new issues about the same problem, just because the previous one has given no solution.
For example, I have a workaround to share for this problem, but it is locked =/ : https://github.com/nestjs/nest/issues/8076
I understand your frustration. Instead of locking issues we could simply unsubscribe from new notifications on them. This is what I've been doing so far. But I can't speak for the others.
But locking is helpful when people don't realize that their comments might be just noise.
Additionally, I strongly recommend you to read this if you want to rely on OSS.
Regarding that issue, I'd like to see your workaround for it in this issue: https://github.com/nestjs/docs.nestjs.com/issues/2823
@micalevisk I agree that I doubt GitHub is the best place to share workarounds or technical discussions, because it must be dedicated for bugs reporting and features improvement only, to avoid to overload the NestJs team. But I find also frustrating that we can do it on generic platforms only, like stackoverflow. It would be great to have a dedicated place somewhere, linked with the official NestJs tool and team, to share our good practices, workarounds and solutions.
@vtgn we use Discord for that. It is pretty big now. In the past others platforms were tried but none succeeded.
@micalevisk Oh ok, I'll try to see it, I have no account yet. Thanks. I'm preparing the answer for the workaround, I need to do some additional tests.
We used to not lock issues in the past and it only led to more spam, making them even harder to follow. If you have a workaround that you'd like to share with others, you can always create a new issue and immediately close it.
