Improvements to Notification Emails
We’ve rolled out several changes to our email notifications. Now you have more ways to filter your email notifications and each email will contain more information about why you received…
We’ve rolled out several changes to our email notifications. Now you have more ways to filter your email notifications and each email will contain more information about why you received it.
Updates to the footer

The footer of every email now indicates why you’ve received a specific correspondence. It contains the same subscription reasons that are available on GitHub.com—for example, whether you or your team were directly mentioned.
If you no longer want to follow a thread, you can mute any new conversations directly from the email. (Note that this will only work for email clients configured to receive HTML emails).
Notification reason as the CC email address

In addition, the same notification reasons exist as a CC email address. This should help with labelling and filtering emails you receive for services like GMail and iCloud that don’t support filtering by our X-GitHub-Reason header.
Our Help documentation provides a full list of the subscription reasons.
We hope these changes enhance your email notification experience!
Written by
Related posts
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.
Introducing Agent HQ: Any agent, any way you work
At Universe 2025, GitHub’s next evolution introduces a single, unified workflow for developers to be able to orchestrate any agent, any time, anywhere.
Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1
In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.