Notification delivery options
You can receive notifications for activity on GitHub in the following locations.
- The notifications inbox in the GitHub web interface
- The notifications inbox on GitHub Mobile, which syncs with the inbox in the web interface
- An email client that uses a verified email address, which can also sync with the notifications inbox in the web interface and GitHub Mobile
Um den Benachrichtigungseingang für GitHub und GitHub Mobile zu verwenden, musst du Benachrichtigungen sowohl für E-Mails als auch für Auf GitHub in deinen Benachrichtigungseinstellungen aktivieren. For more information, see Choosing your notification settings.
Tipp
Wenn du Benachrichtigungen sowohl per E-Mail als auch auf GitHub erhältst, kannst du den Status „Gelesen“ oder „Ungelesen“ der Benachrichtigung automatisch synchronisieren, sodass Benachrichtigungen zu GitHub automatisch als gelesen markiert werden, nachdem du die entsprechende E-Mail-Benachrichtigung gelesen hast. Um diese Synchronisierung zu aktivieren, muss dein E-Mail-Client Bilder von der no-reply
-E-Mail-Adresse für Ihre GitHub Enterprise Server-Instance anzeigen können, die dein Website-Administrator konfiguriert
Benefits of the notifications inbox
The notifications inbox 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 or pull request where the notification originates on GitHub 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.
In addition, you can receive and triage notifications on your mobile device with GitHub Mobile. For more information, see Managing your notification settings with GitHub Mobile or GitHub Mobile.
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.
To see repositories that you're watching, go to your watching page. For more information, see Managing subscriptions for activity on GitHub.
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 (Probleme, Pull Requests, Releases, Sicherheitswarnungen oder Diskussionen) 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. For more information, see Choosing your notification settings.
For example, on your "Notification settings" page:
- If you don't want notifications to be sent to your email, deselect email for participating and watching notifications.
- If you want to receive notifications by email when you've participated in a conversation, then select email under "Participating".
If you do not enable watching or participating notifications for web and mobile, then your notifications inbox will not have any updates.
Customizing your email notifications
After enabling email notifications, GitHub 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 GitHub. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.
Hinweis
Du erhältst nur dann E-Mail-Benachrichtigungen, wenn die Unterstützung für ausgehende E-Mails in Ihre GitHub Enterprise Server-Instance aktiviert ist. Für weitere Informationen kontaktiere deinen Websiteadministrator.
Tipp
Wenn du Benachrichtigungen sowohl per E-Mail als auch auf GitHub erhältst, kannst du den Status „Gelesen“ oder „Ungelesen“ der Benachrichtigung automatisch synchronisieren, sodass Benachrichtigungen zu GitHub automatisch als gelesen markiert werden, nachdem du die entsprechende E-Mail-Benachrichtigung gelesen hast. Um diese Synchronisierung zu aktivieren, muss dein E-Mail-Client Bilder von der no-reply
-E-Mail-Adresse für Ihre GitHub Enterprise Server-Instance anzeigen können, die dein Website-Administrator konfiguriert
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 GitHub you want to receive updates for using your default email address. For example, choose whether you want updates sent 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 Configuring notifications.
You can also send notifications for a specific repository to an email address. For more information, see Informationen zu E-Mail-Benachrichtigungen für Pushvorgänge an dein Repository.
Du erhältst nur Benachrichtigungs-E-Mails, wenn Du E-Mail-Benachrichtigungen in Deinen Benachrichtigungseinstellungen festgelegt hast.
Filtering email notifications
Each email notification that GitHub 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 GitHub contain 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 | GitHub 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 based on the no-reply email address configured by your site administrator. The possible notification reasons are:
|
List-Id field | This field identifies the name of the repository and its owner. The format of this address is always OWNER/REPOSITORY <REPOSITORY.OWNER> , e.g. List-Id: grain-lang/grain <grain.grain-lang.HOSTNAME> . |
X-GitHub-Severity field | E-Mail-Benachrichtigungen für Dependabot alerts, die mindestens ein Repository betreffen, enthalten das Kopfzeilenfeld X-GitHub-Severity . Du kannst den Wert des Kopfzeilenfelds X-GitHub-Severity verwenden, um E-Mail-Benachrichtigungen für Dependabot alerts zu filtern. The possible severity levels are:
|
Replying to email notifications
You can reply to email notifications from GitHub and your reply will be posted to the issue, pull request, or discussion.
The reply-to
address on each email notification identifies the thread and the account that the comment will be posted from. This email address remains valid until you reset your password.
GitHub will not always include the full email contents and will attempt to strip some personally identifiable information from comments created via an email reply:
- Email addresses in a standard format, such as
octocat@github.com
, are transformed to***@***.***
. - Signatures and quoted reply chains, when the email client has used a
>
to mark those sections, are stripped. - While the unsubscribe link from your email notification is sometimes quoted, the link will only work when signed in to your account.
- Email attachments are not included in the resulting comment.
- The maximum length of a comment created via an email reply is 65530 characters.
Choosing your notification settings
-
Klicke in der oberen rechten Ecke einer beliebigen Seite auf .
-
Wähle auf der linken Randleiste unter der Liste der Repositorys das Dropdownmenü „Benachrichtigungen verwalten“ aus, und klicke auf Benachrichtigungseinstellungen.
-
On the notifications settings page, choose how you receive notifications when:
- There are updates in repositories 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 alerts in your repository. For more information, see Dependabot alerts notification options.
- There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see Organization alerts 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 in your notification settings.
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.
For more information, see Configuring notifications.
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 Probleme, Pull Requests, Releases, Sicherheitswarnungen oder Diskussionen (if enabled for the repository), or completely ignore an individual repository.
-
Navigieren Sie auf GitHub zur Hauptseite des Repositorys.
-
In the upper-right corner, select the "Watch" drop-down menu, then click a watch option.
If you want to further customize notifications, click Custom, then select specific events that you want to be notified of, such as Issues or Pull Requests, in addition to participating and @mentions.
For example, if you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
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.
Du erhältst nur Benachrichtigungs-E-Mails, wenn Du E-Mail-Benachrichtigungen in Deinen Benachrichtigungseinstellungen festgelegt hast.
-
Klicke in der oberen rechten Ecke einer beliebigen Seite auf .
-
Wähle auf der linken Randleiste unter der Liste der Repositorys das Dropdownmenü „Benachrichtigungen verwalten“ aus, und klicke auf Benachrichtigungseinstellungen.
-
Under "Default notifications 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.
-
Klicke in der oberen rechten Ecke einer beliebigen Seite auf .
-
Wähle auf der linken Randleiste unter der Liste der Repositorys das Dropdownmenü „Benachrichtigungen verwalten“ aus, und klicke auf Benachrichtigungseinstellungen.
-
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 alerts notification options
The notification options for your user account are available at https://github.com/settings/notifications. You can configure notification settings for each repository, in the repository watch settings.
Um Benachrichtigungen über Dependabot alerts zu Repositorys zu erhalten, müssen Sie diese Repositorys überwachen und den Erhalt von Benachrichtigungen für „Alle Aktivitäten“ abonnieren oder benutzerdefinierte Einstellungen so konfigurieren, dass sie „Sicherheitswarnungen“ umfassen. Weitere Informationen finden Sie unter Configuring notifications. Du kannst die Übermittlungsmethode für Benachrichtigungen sowie die Häufigkeit auswählen, in der die Benachrichtigungen an dich gesendet werden. Wenn deine Unternehmensbesitzerin E-Mail-Benachrichtigungen für deine Instanz konfiguriert hat, erhältst auf den folgenden Kanälen standardmäßig Dependabot alerts:
- In Ihrem Posteingang als Webbenachrichtigungen. Eine Webbenachrichtigung wird gesendet, wenn Dependabot für ein Repository aktiviert ist, eine neue Manifestdatei an das Repository committet wird und ein neues Sicherheitsrisiko mit kritischem oder hohem Schweregrad gefunden wird (Auf GitHub -Option).
- Per E-Mail. Eine E-Mail wird gesendet, wenn Dependabot für ein Repository aktiviert ist, eine neue Manifestdatei an das Repository committet wird und ein neues Sicherheitsrisiko mit kritischem oder hohem Schweregrad gefunden wird (E-Mail-Option).
- Über die Befehlszeile. Warnungen werden als Rückrufe angezeigt, wenn Sie einen Push an Repositorys mit anfälligen Abhängigkeiten durchführen (Option CLI).
- Über GitHub Mobile, als Webbenachrichtigungen. Weitere Informationen finden Sie unter Configuring notifications.
Hinweis
Die E-Mail- und Web-/GitHub Mobile-Benachrichtigungen lauten:
- Pro Repository, wenn Dependabot für das Repository aktiviert ist oder eine neue Manifestdatei an das Repository committet wird.
- Pro Organisation, wenn ein neues Sicherheitsrisiko ermittelt wird.
- Wird gesendet, wenn ein neues Sicherheitsrisiko ermittelt wird. GitHub sendet keine Benachrichtigungen, wenn Sicherheitsrisiken aktualisiert werden.
Du kannst anpassen, wie du über Dependabot alerts benachrichtigt wirst. Beispielsweise kannst du eine wöchentliche Digest-E-Mail erhalten, die Warnungen für bis zu zehn deiner Repositorys über die Optionen Digest-E-Mail mit einer Zusammenfassung der Sicherheitsrisiken senden und Wöchentliche Digest-E-Mail zur Sicherheit zusammenfasst.
For more information about the notification delivery methods available to you, and advice on optimizing your notifications for Dependabot alerts, see Konfigurieren von Benachrichtigungen für Dependabot-Warnungen.
Secret scanning notification options
Wenn ein neues Geheimnis erkannt wird, benachrichtigt GitHub alle Benutzenden mit Zugriff auf Sicherheitswarnungen für das Repository entsprechend ihren Benachrichtigungseinstellungen. Zu diesen Benutzer gehören Folgenden:
- Repositoryadministratoren
- Sicherheitsmanager
- Benutzer*innen mit benutzerdefinierten Rollen mit Lese-/Schreibzugriff
- Organisationsbesitzerinnen und Unternehmensbesitzerinnen, wenn sie Administrator*innen von Repositorys sind, in denen Geheimnisse geleakt wurden
Hinweis
Autoren, die versehentlich Geheimnisse committed haben, werden unabhängig von ihren Benachrichtigungseinstellungen benachrichtigt.
Du erhältst in folgenden Fällen eine E-Mail-Benachrichtigung:
- Du überwachst das Repository.
- Sie haben Benachrichtigungen für "Alle Aktivitäten" oder für benutzerdefinierte "Sicherheitswarnungen" im Repository aktiviert.
- Du hast in deinen Benachrichtigungseinstellungen unter „Abonnements“ > „Beobachten“ ausgewählt, dass du Benachrichtigungen per E-Mail erhalten möchtest.
For more information on how to configure notifications for Warnungen zur Geheimnisüberprüfung, see Überwachen von Warnungen aus der Geheimnisüberprüfung.
GitHub Actions notification options
For repositories that are set up with GitHub Actions and that you are watching, you can choose how you want to receive workflow run updates.
On the "Notification settings" page, select "Email" or "Web" notifications. Optionally, to only receive notifications for failed workflow runs, select "Send notifications for failed workflows only".
Organization alerts notification options
If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", deselect Email.
Managing your notification settings with GitHub Mobile
When you install GitHub Mobile, you will automatically be opted into web notifications. Within the app, you can enable push notifications for the following events.
- Direct mentions
- Assignments to issues or pull requests
- Requests to review a pull request
- Requests to approve a deployment
You can also schedule when GitHub Mobile will send push notifications to your mobile device.
In GitHub Enterprise Server wird ein Hintergrundfetch zum Unterstützen von Pushbenachrichtigungen verwendet, d. h. du erhältst diese möglicherweise verspätet.
Managing your notification settings with GitHub for iOS
- In the bottom menu, tap Profile.
- To view your settings, tap .
- To update your notification settings, tap Notifications and then use the toggles to enable or disable your preferred types of push notifications.
- Optionally, to schedule when GitHub Mobile will send push notifications to your mobile device, tap Working Hours, use the Custom working hours toggle, and then choose when you would like to receive push notifications.
Managing your notification settings with GitHub for Android
- In the bottom menu, tap Profile.
- To view your settings, tap .
- To update your notification settings, tap Configure Notifications and then use the toggles to enable or disable your preferred types of push notifications.
- Optionally, to schedule when GitHub Mobile will send push notifications to your mobile device, tap Working Hours, use the Custom working hours toggle, and then choose when you would like to receive push notifications.
Configuring your watch settings for an individual repository with GitHub Mobile
You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of new releases, or completely ignore an individual repository.
- On GitHub Mobile, navigate to the main page of the repository.
- Tap Watch.
- To choose what activities you receive notifications for, tap your preferred watch settings. For example, choose to only be notified when you are participating or @mentioned, or use the "Custom" option to select specific events that you want to be notified of.