Notification delivery options
You can receive notifications for activity on 您的企业 in the following locations.
- The notifications inbox in the 您的企业 web interface
- An email client that uses a verified email address, which can also sync with the notifications inbox on 您的企业
提示:如果您同时接收 Web 和电子邮件通知,您可以自动同步通知的已读或未读状态,以便在您阅读相应的电子邮件通知后,Web 通知自动标记为已读。 要启用此同步,您的电子邮件客户端必须能够查看来自 无需回复
电子邮件地址 您的 GitHub AE 主机名的图像。
Benefits of the notifications inbox
The notifications inbox on 您的企业 includes triaging options designed specifically for your GitHub notifications flow, including options to:
- Triage multiple notifications at once.
- Mark completed notifications as Done and remove them from your inbox. To view all of your notifications marked as Done, use the
is:done
query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the
is:saved
query. - Unsubscribe and remove a notification from your inbox.
- Preview the issue, pull request, or team discussion where the notification originates on 您的企业 from within the notifications inbox.
- See one of the latest reasons you're receiving a notification from your inbox with a
reasons
label. - Create custom filters to focus on different notifications when you want.
- Group notifications in your inbox by repository or date to get a quick overview with less context switching
Benefits of using an email client for notifications
One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on GitHub unless you've marked them as Saved. Saved notifications are kept indefinitely. For more information about your inbox's retention policy, see "About notifications."
Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "Customizing your email notifications."
About participating and watching notifications
When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "About team discussions."
To see repositories that you're watching, go to your watching page. For more information, see "Managing subscriptions and notifications on GitHub."
Configuring notifications
You can configure notifications for a repository on the repository page, or on your watching page.
About custom notifications
You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ( 议题、拉取请求、发布或讨论 ) happen within a repository, or ignore all notifications for a repository. For more information, see "Configuring your watch settings for an individual repository" below.
Participating in conversations
Anytime you comment in a conversation or when someone @mentions your username, you are participating in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking Unsubscribe on the issue or pull request or through the Unsubscribe option in the notifications inbox.
For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on 您的企业.
For example:
- If you don't want notifications to be sent to your email, unselect email for participating and watching notifications.
- If you want to receive notifications by email when you've participated in a conversation, then you can select email under "Participating".
If you do not enable watching or participating notifications for web, then your notifications inbox will not have any updates.
Customizing your email notifications
After enabling email notifications, 您的企业 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 您的企业. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.
注:如果在 您的企业 上启用了出站电子邮件支持,您将只收到邮件通知。 更多信息请联系站点管理员。
提示:如果您同时接收 Web 和电子邮件通知,您可以自动同步通知的已读或未读状态,以便在您阅读相应的电子邮件通知后,Web 通知自动标记为已读。 要启用此同步,您的电子邮件客户端必须能够查看来自 无需回复
电子邮件地址 您的 GitHub AE 主机名的图像。
Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on 您的企业 you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:
- Comments on issues and pull requests.
- Pull request reviews.
- Pull request pushes.
- Your own updates, such as when you open, comment on, or close an issue or pull request.
Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "Choosing where your organization’s email notifications are sent."
You can also send notifications for a specific repository to an email address. For more information, see "About email notifications for pushes to your repository."
只有在通知设置中选择了接收电子邮件通知时,才会收到通知电子邮件。
Filtering email notifications
Each email notification that 您的企业 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.
If you believe you're receiving notifications that don't belong to you, examine the X-GitHub-Recipient
and X-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.
Email notifications from 您的企业 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. |
Cc address | GitHub AE 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 基于站点管理员配置的无需回复电子邮件地址. The possible notification reasons are:
|
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>.[hostname] . |
X-GitHub-Severity field | 影响一个或多个存储库的 Dependabot 警报 的电子邮件通知包括 X-GitHub-Severity 标头字段。 可以使用 X-GitHub-Severity 标头字段的值来筛选电子邮件通知中的 Dependabot 警报。 The possible severity levels are:
|
Choosing your notification settings
- 在任何页面的右上角,单击 。
- 在左侧边栏中的仓库列表下,使用“Manage notifications(管理通知)”下拉按钮单击 Notification settings(通知设置)。
- On the notifications settings page, choose how you receive notifications when:
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "About participating and watching notifications."
- You gain access to a new repository or you've joined a new team. For more information, see "Automatic watching."
- There are new Dependabot 警报 in your repository. For more information, see "Dependabot 警报 notification options."
Automatic watching
By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.
If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
Configuring your watch settings for an individual repository
You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of certain event types such as 议题、拉取请求、发布或讨论 (if enabled for the repository) , or completely ignore an individual repository.
-
在 您的企业 上,导航到仓库的主页面。
-
In the upper-right corner, select the "Watch" drop-down menu to click a watch option.
Choosing where your organization’s email notifications are sent
If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.
只有在通知设置中选择了接收电子邮件通知时,才会收到通知电子邮件。
- 在任何页面的右上角,单击 。
- 在左侧边栏中的仓库列表下,使用“Manage notifications(管理通知)”下拉按钮单击 Notification settings(通知设置)。
- Under "Default notification email", select the email address you'd like notifications sent to.
- Click Save.
Customizing email routes per organization
If you are a member of more than one organization, you can configure each one to send notifications to any of the email addresses for your account.
- 在任何页面的右上角,单击 。
- 在左侧边栏中的仓库列表下,使用“Manage notifications(管理通知)”下拉按钮单击 Notification settings(通知设置)。
- Under "Custom routing," find your organization's name in the list.
- Click Edit next to the email address you want to change.
- Select one of your verified email addresses, then click Save.
Dependabot 警报 notification options
您可以选择通知的传递方式,以及向您发送通知的频率。
By default, if your enterprise owner has configured email for notifications on your instance, you will receive Dependabot 警报:
- by email, an email is sent when Dependabot is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (Email each time a vulnerability is found option).
- in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (UI alerts option).
- on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (Command Line option).
- in your inbox, as web notifications. A web notification is sent when Dependabot is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (Web option).
Note: The email and web notifications are:
-
per repository when Dependabot is enabled on the repository, or when a new manifest file is committed to the repository.
-
per organization when a new vulnerability is discovered.
You can customize the way you are notified about Dependabot 警报. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the Email a digest summary of vulnerabilities and Weekly security email digest options.
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for Dependabot 警报, see "Configuring notifications for vulnerable dependencies."