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.

Email format

"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.

The From address

The From address in all GitHub Enterprise notification emails is the no-reply email address configured by your site administrator.

The To address

The 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.

The Cc address

If you're subscribed to a conversation and have enabled email notifications, GitHub Enterprise will Cc you on notification emails.

In addition, there's a second Cc email address that matches the notification reason. The suffix for all of these notification reasons is the no-reply email address configured by your site administrator. The possible notification reasons are:

Reason Description
assign You were assigned to an issue or pull request.
author You created an issue or pull request.
comment You commented on an issue or pull request.
mention You were mentioned on an issue or pull request.
milestone A milestone you're subscribed to was mentioned on an issue or a pull request.
push Someone committed to a pull request you're subscribed to.
state_change An issue or pull request you're subscribed to was either closed or opened.
team_mention A team you belong to was mentioned on an issue or pull request.
your_activity You opened, commented on, or closed an issue or pull request.

The mailing list address

The 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].

Further reading