-
Notifications
You must be signed in to change notification settings - Fork 212
Make default comment friendlier and actionable (fixes #67) #162
Conversation
@bkeepers Is there anything I can do to help move this forward? I'd love to see this merged. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
I think this is just awaiting a review and a merge. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
I think this is just awaiting a review and a merge. |
@bkeepers This issue seems to need your attention... Maybe you can invite some collaborators to help with reviewing and merging PRs? |
I am no longer involved with the project. Maybe @tcbyrd or @JasonEtco could suggest someone that can help? |
@bkeepers Ok clear, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @waldyrious 👋 Apologies for the delay. I think this is a welcome change. I've left a note about clarifying the comment, and making sure that folks that see it understand what will happen. If you can make that change, this should be good to go!
Maybe we could just concat the two?
|
Thanks @JasonEtco and @christianbundy for the suggestions. I re-added the note at the end, but removed the "Thank you for your contributions" because it sounds a little passive-aggressive to me coming after a "this issue will be closed" message. Let me know what you think. :) |
Also, I wonder if moving the placement of "automatic" to the closure sentence could help reduce the chance of perceived harshness, by clarifying that no decision for closure has been made yet:
WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's perfect @waldyrious! Thanks for the contribution, and thank you for your patience in getting this merged!
The default message posted by the bot is unnecessarily harsh and final-sounding, which has resulted in a lot of grief, summarized in #67.
Interestingly enough, even this repo decided against using the default message and has been using a friendlier and more constructive message for a while.
This change makes that message the default, so that other communities using this bot get a more positive experience out of the box.