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.
| Header | Information |
|---|---|
From address | This address will always be notifications@github.com or notifications@SUBDOMAIN.ghe.com. |
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 @noreply.github.com or @noreply.SUBDOMAIN.ghe.com. 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.github.com>. |
X-GitHub-Severity field | 하나 이상의 리포지토리에 영향을 주는 Dependabot alerts에 대한 메일 알림에는 X-GitHub-Severity 헤더 필드가 포함됩니다. X-GitHub-Severity 헤더 필드 값을 사용하여 Dependabot alerts에 대한 메일 알림을 필터링할 수 있습니다. The possible severity levels are:
|