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
Here is my suggestion for a bot template to close an issue, label it as "no-template" and give a feedback to the user.
This is for closing issues that do not adhere to the issue template. This is one of the most important templates when it comes to wording, as it must be concise, clear and friendly and explain why it is not optional. I hope I have achieved that with the text below. If not, please suggest alterations :)
Cheers
Thomas
Hi [REPORTER USERNAME]
I am temporarily closing this issue as you have not used our issue template (the text that is already filled in automatically, when you open a new issue). Please understand, that in order to solve your issue as fast as possible, we need to understand your issue and your setup as good as possible to first reproduce it on our side and then fix it.
Therefore, we kindly ask you to adhere to the issue template and provide us with the information we need. For that, please edit your inital post rather than replying with the issue template. We will then have a look at your feedback and re-open the issue.
This benefits all users as we are able to understand and fix issues faster. Thank you for understanding and being kind to us and others :)
[GENERIC ROCKET.CHAT SALUTATION]
[USERNAME OF THE ONE WHO TRIGGERED THE BOT]
The text was updated successfully, but these errors were encountered:
Usage:
@rocket-cat notemplate+close [REPORTER USERNAME]
Here is my suggestion for a bot template to close an issue, label it as "no-template" and give a feedback to the user.
This is for closing issues that do not adhere to the issue template. This is one of the most important templates when it comes to wording, as it must be concise, clear and friendly and explain why it is not optional. I hope I have achieved that with the text below. If not, please suggest alterations :)
Cheers
Thomas
The text was updated successfully, but these errors were encountered: