You can receive your notifications on GitHub or have them delivered through your email client.

For personal accounts, notification emails are automatically sent to your primary email address. You can also manage which verified email address organizations should send notifications to.

Choosing the delivery method for notifications about repository activity

  1. In the upper-right corner of any page, click your profile photo, then click Settings. Settings icon in the user bar
  2. In the user settings sidebar, click Notifications. Notification center

  3. Configure how you would like to receive notifications you either participate in or watch by selecting the checkboxes:

    Configuring notification settings

  4. If you selected Email for conversations you're either participating in or watching, choose which updates you receive by selecting the checkboxes in the "Notification email" section:

    • Select Comments on Issues and Pull Requests to receive an email when someone makes a comment in an issue or in the "Conversation" tab of a pull request.
    • Select Pull request reviews to receive an email when someone makes a review comment in the "Files changed" tab of a pull request.
    • Select Pull request pushes to receive an email when someone adds commits to a pull request that you're subscribed to.
    • Select Include your own updates to receive an email when you open, comment on, or close an issue or pull request. Configuring email notification options

Choosing the delivery method for security alerts for vulnerable dependencies

If your repository has a dependency manifest in Ruby or JavaScript (and if you've set up the dependency graph if it's a private repository), you can choose to receive security alerts when GitHub detects a vulnerable dependency in your repository. You can configure your security alerts as web notifications, email notifications, or alerts in the GitHub interface. For more information, see "About security alerts for vulnerable dependencies."

  1. In the upper-right corner of any page, click your profile photo, then click Settings. Settings icon in the user bar
  2. In the user settings sidebar, click Notifications. Notification center

  3. Under "Vulnerability alerts", configure how you would like to receive notifications when GitHub detects a vulnerable dependency in your repository:

Choosing the notification delivery method for organizations you belong to

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.

Tip: You'll only receive notification emails if you've chosen to receive email notifications in your notification settings.

  1. In the upper-right corner of any page, click your profile photo, then click Settings. Settings icon in the user bar
  2. In the user settings sidebar, click Notifications. Notification center

  3. In the "Primary email address" list, select the email address you'd like notifications sent to. Primary email address drop-down

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 your verified email addresses.

  1. In the upper-right corner of any page, click your profile photo, then click Settings. Settings icon in the user bar
  2. In the user settings sidebar, click Notifications. Notification center

  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

Further reading