-
Notifications
You must be signed in to change notification settings - Fork 126
Make ansibot less chatty #1081
Comments
I think that everyone deserves to be thanked. As of other points, I 100% agree with those. |
Hi,
|
@gundalow Perfect. I also wonder whether we can make this shorter for regular contributors. They don't need to be forwarded to working groups or being lectured about the process. It just adds more noise to the thread IMO. Less is more. @webknjaz Being thanked by a bot doesn't feel very special to me. I don't think it's very flattery, but I can imagine new contributors are more affected by it. |
I prefer one email for a PR instead of three. It's also annoying that you get a single email for every single code comment, but I assume this is a Github thing and not related to ansibot. |
@ckotte yes, that's github's setting. You can configure that in your own notification settings. |
This comment has been minimized.
This comment has been minimized.
@dagwieers yup, will do |
As this was posted as it's own comment, it was found to be a bit spammy. The long term fix for this is to have a *single* message when Issues/PRs are created, see ansible#1081 (comment)
As this was posted as it's own comment, it was found to be a bit spammy. The long term fix for this is to have a *single* message when Issues/PRs are created, see #1081 (comment)
"Thanks" message has been removed |
I understand the need for presenting more information to (new) users, but having multiple comments added in close succession is a bit too much. Each comment induces another mail.
Example: ansible/ansible#47271 (comment)
For a typical new PR/issue we get:
Each of these comments link to the ansibot help documentation.
Could we make ansibot smarter so it combines this information in a single comment ? Especially 1. and 3. seem a good introductionary blob, but I would also include the other authors by replacing cc @author1 @author2 with The following people are now notified of your issue/PR: @author1 @author2 (we could even make a distinction between maintainers and people notified in that message if that is deemed useful)
The text was updated successfully, but these errors were encountered: