From 2a3a87daf833bede15917ec55a9eab4eb1db6d2c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=A9=8D=E4=B8=B9=E5=B0=BC=20Dan=20Jacobson?= Date: Thu, 5 Nov 2020 21:23:39 +0800 Subject: [PATCH] Explain critical blocking feature that causes tremendous misunderstandings I've seen it a 1000 times: User A gets angrier and angrier because User B is not responding, even to @mentions. That's because User A never read that blocking actually prevents User B from getting the message. This has exacerbated friction on teams I have worked with and needs to be documented. --- .../blocking-a-user-from-your-personal-account.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md b/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md index 6cdae5472924..5f1e39664dae 100644 --- a/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md +++ b/content/github/building-a-strong-community/blocking-a-user-from-your-personal-account.md @@ -49,6 +49,9 @@ In repositories you own, blocked users also cannot: - Comment on issues, pull requests, or commits - Add or edit wiki pages +(Keep in mind users you block will not receive email notifications of +comments you make, even if [@mentioning](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) them directly.) + ### Blocking a user in your account settings {% data reusables.user_settings.access_settings %}