|
|
|
|
@@ -16,6 +16,7 @@ redirect_from:
|
|
|
|
|
versions:
|
|
|
|
|
free-pro-team: '*'
|
|
|
|
|
enterprise-server: '>=2.21'
|
|
|
|
|
github-ae: '*'
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
### Notification delivery options
|
|
|
|
|
@@ -108,9 +109,9 @@ Email notifications from {% data variables.product.product_name %} contain the f
|
|
|
|
|
| Header | Information |
|
|
|
|
|
| --- | --- |
|
|
|
|
|
| `From` address | This address will always be {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
|
|
|
|
|
| `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: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
|
|
|
|
| `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 == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}
|
|
|
|
|
| `To` field | This field connects directly to the thread.{% if currentVersion != "github-ae@latest" %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
|
|
|
|
|
| `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: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li>{% if currentVersion != "github-ae@latest" %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li>{% endif %}<li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
|
|
|
|
| `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 == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
|
|
|
|
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %}
|
|
|
|
|
|
|
|
|
|
### Choosing your notification settings
|
|
|
|
|
@@ -152,11 +153,12 @@ If you are a member of more than one organization, you can configure each one to
|
|
|
|
|
{% data reusables.notifications-v2.manage-notifications %}
|
|
|
|
|
3. Under "Custom routing," find your organization's name in the list.
|
|
|
|
|
|
|
|
|
|
4. Click **Edit** next to the email address you want to change.
|
|
|
|
|
4. Click **Edit** next to the email address you want to change.
|
|
|
|
|
|
|
|
|
|
5. Select one of your verified email addresses, then click **Save**.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{% if currentVersion != "github-ae@latest" %}
|
|
|
|
|
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
|
|
|
|
### {% data variables.product.prodname_dependabot_alerts %} notification options
|
|
|
|
|
{% else %}
|
|
|
|
|
@@ -167,9 +169,9 @@ If you are a member of more than one organization, you can configure each one to
|
|
|
|
|
{% data reusables.notifications.vulnerable-dependency-notification-options %}
|
|
|
|
|
|
|
|
|
|
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."
|
|
|
|
|
{% endif %}
|
|
|
|
|
|
|
|
|
|
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
|
|
|
|
|
|
|
|
|
### {% data variables.product.prodname_actions %} notification options
|
|
|
|
|
|
|
|
|
|
Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.
|
|
|
|
|
@@ -179,7 +181,6 @@ Choose how you want to receive workflow run updates for repositories that you ar
|
|
|
|
|
{% endif %}
|
|
|
|
|
|
|
|
|
|
{% if currentVersion == "free-pro-team@latest" %}
|
|
|
|
|
|
|
|
|
|
### Enabling push notifications with {% data variables.product.prodname_mobile %}
|
|
|
|
|
|
|
|
|
|
When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. You can then enable push notifications for direct mentions within the app.
|
|
|
|
|
|
Laura Coursen