-
Notifications
You must be signed in to change notification settings - Fork 31
Information on issue message and call to action #147
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
Comments
Thank you for the issue.
Yes. Carson is aware of the response but it (he?) is not aware of the context. (ie, what you write) So if the issue has been resolved, I would expect the user to say "yes" and then close the issue. We spent some time in #109 figuring out what the message would be. It may not be perfect so I would be happy to get suggestions for improvement. The important thing for this message is that we encourage the users to take an action, either making a comment or closing the issue. |
@Nyholm i see better with the comment so thx for the bot comment, i would propose to clearly write the possible actions the user has regarding its issue because the before
after
or something like that, so |
Thank you. There is a second message that will be posted on your issue in about a weeks time. It will inform you about closing the issue. So the point of the first message should not be to close the issue, it should more be like "hey, is this relevant?, can somebody look at this?". |
I see, lets close this issue then 👍 |
Hi,
On a (long ago) forgot issue I have, I just saw in GH notification of @carsonbot
Is the bot aware of responses ? If we wrote
no
etc ? Because like that, this message feel like a bottle thrown into the sea.If yes, could be usefull to write it in the mesasge :) (like dependabot)
If no, maybe write what are the call to action expected after this message so that the dev can take action on that :)
I obviously understand the main aim of this bot, but felt like this specific message is not well understandable, thus this issue
Thank you,
The text was updated successfully, but these errors were encountered: