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
10 technical talks I’m excited about at GitHub Universe 2026
From verifying AI-written code to securing npm dependencies, these are the sessions I’m building my Universe agenda around.
Developer policy update: Transparency, state policy, and what’s ahead
Explore GitHub’s latest transparency data and learn more about policy updates affecting developers and open source.
Developers want more efficient software. Here’s what over 1,000 GitHub users told us they need.
New research from GitHub and Yale Program on Climate Change Communication finds strong demand for tools, measurement, and practical guidance that can help developers reduce wasted compute.