bernhold
commented
5 years ago The notification email GitHub sends have a well-documented structure for the From, cc, and Subject fields that can be used to implement mail filters to help manage the notifications you receive.
https://help.github.com/en/github/receiving-notifications-about-activity-on-github/about-email-notifications is the place to look for the details.
To summarize:
From:will always benotifications@github.comTo:will be related to the repository (organization/repository)Subject:will include the repository and issue/pr title and numberCc:will include- your email, if you are subscribed to the conversation
- a reason for the notification, in the form of an email address like
reason@noreply.github.com. There are 12 different reasons associated with GitHub notifications, which are detailed on the page cited above.
I’ve started looking at the notifications question.
First of all, you can get notifications through a web interface and/or through email. You can make this choice by default, and I think you can tailor it per project. So if you have a preference for looking at the web site on a regular basis, that might be one thing to consider.
And GitHub itself offers some suggestions for reducing your notification traffic: https://github.blog/2017-07-18-managing-large-numbers-of-github-notifications/ It amounts to unsubscribing from projects that you don’t want/need notifications for. You can also tweak a little bit the “level” of notifications that you get. It may sound obvious, but if you’re like me, you end up getting automatically subscribed to a lot of repos that you might have minimal involvement with.
Part 2 will involve filtering/tagging the notifications you do receive so that you can process them more efficiently. I’m hoping to develop a “recommended EB filtering strategy” as part of it, so that may take a little more time.