jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-30 12:02:01 -05:00
Code Issues Projects Releases Wiki Activity
Files
cf968af10316c4483eafac673eb2c5261cced1de
docs/content/github/receiving-notifications-about-activity-on-github/about-email-notifications.md
Sarah Schneider f272eec944 Remove deprecated GHES versions from content and data (#15830) 
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script)

* package-lock

* turn elsif into two ifs to prepare for running Liquid deprecation script

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.)

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.15

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.17

* ran script/remove-deprecated-enterprise-version-markup.js --release 2.18

* update hardcoded test

* Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

* add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
2020-10-01 10:55:34 -04:00

4.6 KiB
Raw Blame History

title, intro, versions
title intro versions
About email notifications When you enable email notifications, you will receive participating and watching notifications in your email client, and you can filter them using the email header information.
enterprise-server
<2.21

For more information about the differences between participating and watching notifications, see "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)."

After enabling email notifications, {% data variables.product.product_name %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_name %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. For more information about enabling email notifications, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."

{% data reusables.notifications.outbound_email_tip %}

{% data reusables.notifications.shared_state %}

Filtering email notifications

Each email notification that {% data variables.product.product_name %} 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 {% data variables.product.product_name %} notifications, or certain types of {% data variables.product.product_name %} notifications.

Email notifications from {% data variables.product.product_name %} contain the following header information:

Header Information
From address This address will always be 'the no-reply email address configured by your site administrator'.
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 {% data variables.product.product_name %} will Cc you if you're subscribed to a conversation. The second Cc email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • 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.
  • manual: There was an update to an issue or pull request you manually subscribed to.
  • mention: You were mentioned on an issue or pull request.
  • push: Someone committed to a pull request you're subscribed to.
  • review_requested: You or a team you're a member of was requested to review a pull request.
  • security_alert: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive security alerts for.
  • state_change: An issue or pull request you're subscribed to was either closed or opened.
  • subscribed: There was an update in a repository you're watching.
  • 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.
mailing list field This field identifies the name of the repository and its owner. The format of this address is always <repository name>.<repository owner>.{% data variables.command_line.backticks %}. {% if currentVersion ver_gt "enterprise-server@2.19" % %}
X-GitHub-Severity field {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • low
  • moderate
  • high
  • critical
For more information, see "About alerts for vulnerable dependencies."

Further reading

  • "[Listing the repositories you're watching](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)"
  • "[Watching and unwatching repositories](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)"
  • "[Subscribing to and unsubscribing from notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)"
  • "Creating gists"
Reference in New Issue View Git Blame Copy Permalink