-
Notifications
You must be signed in to change notification settings - Fork 16
Send notifications to DM instead of code review channels #46
Conversation
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.
👍 looks good
@@ -676,6 +677,7 @@ class CodeReviews | |||
newStatus = false | |||
message = "Hey @#{cr.user.name}, looks like *#{cr.slug}* was closed on GitHub." + | |||
" Say `ignore #{cr.slug}` to remove it from the queue." |
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.
Since every room can have it's own code review queue... and this message used to appear in-channel to identify which queue/channel, it seems like we might want to append the channel name to this message in some manner
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 it's worth adding the channel name to the DM for context, but I will look at doing this shortly (so you don't need to)
I agree, I'd started work on this and subsequently got swamped by end of year client work. Thanks for picking this up, I think this is a huge win for developer experience in code review. |
Something we had discussed in Tech CoP Planning was removing the alert that is sent to #codereview when changes are requested. This PR is an attempt at starting that process.
Reasoning
What this PR does is remove all public messages to the channel, instead directing the generic message to the correct recipient--either the reviewer, or the submitter. The reasoning for this is simple: They were already the intended recipient of the message. The message they receive asks them to perform optional tasks, which are unlikely to be performed by anybody else on staff even if they do happen to see the message.
Due to this, it is my belief that very little will change in workflow with this change, except the removal of what can sometimes feel like an unintentional public shaming when we request changes. The hope is that this will lead to reviewers feeling more comfortable with using this option.