You can choose to receive emails about changes made to repositories, issues, or pull requests that you have access to. The metadata of each email you receive is specific to the type of notification the email is addressing so you can filter emails from GitHub Enterprise in your email client.
You will only receive email notifications if outbound email support is enabled on your GitHub Enterprise instance. For more information, contact your site administrator.
"If you've enabled email notifications, you'll receive multipart emails that contain both HTML and plain text copies of the email content, including Markdown, @mentions, emojis, hash-links, and more. You can configure your client to select and display only the plain text copy.
We'll automatically format Markdown, @mentions, emojis, hash-links, and more in the HTML copy.
If you only want to see the email text, you can configure your client to select and display only the plain text copy.
Unified mail headers
To help you filter or forward notifications that GitHub Enterprise sends, header information in every email is consistent.
From address in all GitHub Enterprise notification emails is the no-reply email address configured by your site administrator.
To field in the email connects directly to the thread. That means that if you reply to the email, you'll actually be adding a new comment to the conversation.
Inbound email support must be enabled on your GitHub Enterprise instance in order for email replies to notifications to work. For more information, contact your site administrator.
mailing list address
mailing list field in every email identifies the name of the repository and its owner. The format of this address is always
<repository name>.<repository owner>.[hostname].