You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is Your Feature Request Related To A Problem? Please describe.
It would be helpful to have a way to lock threads that have been fixed, or at the very least those that are closed. Suggesting to add it here, so it can be rolled out to other repositories using the file synchronization that are already in play.
Describe The Solution. Why is it needed?
One solution would be to use the github action workflow called lock-threads and should probably be called multiple times, so it can give context specific issue comments, specific lock reasons and so on.
I propose that we treat released bug issues specifically by adding a comment to the thread that the bug is considered fixed, and any regressions need a new issue.
Additionally, any issue that have been closed and do not have any of the state labels on them, should be locked with a different reason than the default (the default is resolved).
Additional Context.
There are quite often that users comment on already closed threads that have been released instead of opening a new issue for regressions.
Related Issues
N/A
The text was updated successfully, but these errors were encountered:
Is Your Feature Request Related To A Problem? Please describe.
It would be helpful to have a way to lock threads that have been fixed, or at the very least those that are closed. Suggesting to add it here, so it can be rolled out to other repositories using the file synchronization that are already in play.
Describe The Solution. Why is it needed?
One solution would be to use the github action workflow called
lock-threads
and should probably be called multiple times, so it can give context specific issue comments, specific lock reasons and so on.I propose that we treat released bug issues specifically by adding a comment to the thread that the bug is considered fixed, and any regressions need a new issue.
Additionally, any issue that have been closed and do not have any of the state labels on them, should be locked with a different reason than the default (the default is
resolved
).Additional Context.
There are quite often that users comment on already closed threads that have been released instead of opening a new issue for regressions.
Related Issues
N/A
The text was updated successfully, but these errors were encountered: