Email notification headers
Learn how to filter email notifications by using information in the headers.
Each email notification that GitHub sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all GitHub notifications, or certain types of GitHub notifications.
Note
If you believe you're receiving notifications that don't belong to you, examine theX-GitHub-Recipient andX-GitHub-Recipient-Address headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.
| Header | Information |
|---|---|
From address | This address will always benotifications@github.com. |
To field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. |
Cc address | GitHub willcc you if you're subscribed to a conversation. The secondcc email address matches the notification reason. The suffix for these notification reasons is@noreply.github.com. The possible notification reasons are:
|
List-Id field | This field identifies the name of the repository and its owner. The format of this address is alwaysOWNER/REPOSITORY <REPOSITORY.OWNER>, e.g.List-Id: grain-lang/grain <grain.grain-lang.github.com>. |
X-GitHub-Severity field | Email notifications for Dependabot alerts that affect one or more repositories include theX-GitHub-Severity header field. You can use the value of theX-GitHub-Severity header field to filter email notifications for Dependabot alerts. The possible severity levels are:
|