Conceptual illustration of the retired repository push-email connection. Illustration: MacDigest.
GitHub stopped sending its legacy repository push-event emails on October 15, 2026. Mac and iOS teams that routed commit summaries into a shared mailbox should check whether they depended on that integration: a quiet mailbox can now reflect its retirement even while developers continue pushing code.
Which email stream ended
The retired integration was configured by repository administrators under Settings, Integrations, Email notifications. GitHub’s earlier documentation describes messages listing new commits and linking to their diff, with delivery to specified addresses, including a group mailbox.
GitHub says it removed the feature to reduce spam and abuse because recipients did not have to agree to receive the messages. The old setup-page URL now redirects to GitHub’s general notifications guide. Older enabling instructions do not override the October 15 retirement notice.
Here, push means sending code to a repository. GitHub’s separate notification documentation still covers watching, participation, pull-request reviews, security alerts and iPhone push notifications. Those systems are outside this retirement notice.
Replace the commit-mail workflow
For teams that still need these emails, GitHub suggests an Actions workflow triggered by pushes, using the team’s own SMTP server or email provider. The announcement describes a replacement teams must arrange, with no automatic migration offered.
First identify which repositories fed the shared inbox and who used those messages. Check recent commits directly in GitHub while deciding whether to restore a mail-based workflow. Avoid treating missing mail as evidence that a branch has been inactive.
