Skip to main content
GitHub AEは、現在限定リリース中です。詳細については営業チームにお問い合わせください。

Configuring notifications

Choose the type of activity on GitHub that you want to receive notifications for and how you want these updates delivered.

Notification delivery options

You can receive notifications for activity on your enterprise in the following locations.

  • The notifications inbox in the your enterprise web interface
  • An email client that uses a verified email address, which can also sync with the notifications inbox on your enterprise

Tip: Web通知とメール通知の両方を受信する場合、通知の既読あるいは未読状態を自動的に同期して、対応するメール通知を読んだら自動的にWeb通知が既読としてマークされるようにできます。 この同期を有効化するには、メールクライアントはGitHub AEのホスト名のno-replyメールアドレスからの画像を表示できなければなりません。

Benefits of the notifications inbox

The notifications inbox on your enterprise 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 your enterprise 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 (issues, pull requests, releases, or discussions ) 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 your enterprise.

Participating and watching notifications options

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, your enterprise 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 your enterprise. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.

ノート: メール通知は、your enterpriseでアウトバウンドメールサポートが有効化されている場合にのみ受信できます。 詳しい情報については、サイト管理者にお問い合わせください。

Tip: Web通知とメール通知の両方を受信する場合、通知の既読あるいは未読状態を自動的に同期して、対応するメール通知を読んだら自動的にWeb通知が既読としてマークされるようにできます。 この同期を有効化するには、メールクライアントはGitHub AEのホスト名のno-replyメールアドレスからの画像を表示できなければなりません。

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 your enterprise 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 your enterprise 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 your enterprise contain the following header information:

From addressThis address will always be 'the no-reply email address configured by your site administrator'.
To fieldThis field connects directly to the thread.
Cc addressGitHub 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 サイト管理者が設定した no-reply メールアドレスに基づく. The possible notification reasons are:
  • assign: You were assigned to an issue or pull request.
  • author: You created an issue or pull request.
  • ci_activity: A GitHub Actions workflow run that you triggered was completed.
  • 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: GitHub detected a vulnerability in a repository you receive 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 fieldThis 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 fieldEmail notifications for Dependabotアラート that affect one or more repositories include the X-GitHub-Severity header field. You can use the value of the X-GitHub-Severity header field to filter email notifications for Dependabotアラート. The possible severity levels are:
  • low
  • moderate
  • high
  • critical
For more information, see "About Dependabotアラート."

Choosing your notification settings

  1. 任意のページの右上で をクリックします。 未読メッセージを示す通知
  2. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[Notification settings] をクリックします。 [Manage notifications] ドロップダウンメニューオプション
  3. On the notifications settings page, choose how you receive notifications when:

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.

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 issues, pull requests, releases, or discussions (if enabled for the repository) , or completely ignore an individual repository.

  1. your enterpriseで、リポジトリのメインページにアクセスしてください。

  2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option.

    Watch options in a drop-down menu for a repository

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.


  1. 任意のページの右上で をクリックします。 未読メッセージを示す通知
  2. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[Notification settings] をクリックします。 [Manage notifications] ドロップダウンメニューオプション
  3. Under "Default notification email", select the email address you'd like notifications sent to. Default notification email address drop-down
  4. 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.

  1. 任意のページの右上で をクリックします。 未読メッセージを示す通知
  2. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[Notification settings] をクリックします。 [Manage notifications] ドロップダウンメニューオプション
  3. Under "Custom routing," find your organization's name in the list. List of organizations and email addresses
  4. Click Edit next to the email address you want to change. Editing an organization's email addresses
  5. Select one of your verified email addresses, then click Save. Switching your per-org email address

Dependabotアラート notification options

You can choose the delivery method for notifications, as well as the frequency at which the notifications are sent to you.

By default, if your enterprise owner has configured email for notifications on your instance, you will receive Dependabotアラート:

  • メールについては、Dependabotがリポジトリで有効化された場合、新しいマニフェストファイルがリポジトリにコミットされた場合、重要度が重大もしくは高の新しい脆弱性が見つかった場合に送信されます(Email each time a vulnerability is found(脆弱性が見つかるたびにメールする)オプション)。
  • ユーザインターフェースについては、脆弱な依存関係があった場合に、リポジトリのファイルとコードビューに警告が表示されます(UI alerts(UIアラート)オプション)。
  • コマンドラインについては、脆弱な依存関係を伴うプッシュをリポジトリに対して行った場合、コールバックとして警告が表示されます(Command Line(コマンドライン)オプション)。
  • インボックスについては、Web通知として表示されます。 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:

  • リポジトリごと Dependabotがリポジトリで有効化された場合、あるいは新しいマニフェストファイルがリポジトリにコミットされた場合。

  • Organizationごと 新しい脆弱性が見つかった場合。


Dependabotアラートについて受ける方法は、カスタマイズできます。 たとえば、Email a digest summary of vulnerabilities(脆弱性のダイジェストサマリーメール)及びWeekly security email digest(週間のセキュリティメールダイジェスト)オプションを使って、最大10件のリポジトリに関するアラートをまとめた週間のダイジェストメールを受信できます。

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