← Back

Wire · technology

GitHub stopped repository push emails — the replacement moves consent, secrets and cost to you

Published

16 October 2026

Topic

technology

◆ Sectors

Developer Tools

◆ Geography

United States

◆ Source

Read at opentools.ai →

◆ Verified

Fusion42 · 16 October 2026 · Fusion42 review

GitHub has stopped sending repository push-event emails due to spam and abuse concerns and recommends using a push-triggered GitHub Actions workflow connected to the organization's SMTP server as a replacement, shifting responsibility for recipient management, credentials, and delivery costs to repository owners.

This Wire brief sits within Fusion42's coverage of Developer Tools.

◆ ◆ The Wire takeaway

You must rebuild push notifications using workflows and your own email system rather than relying on GitHub’s free emails. That creates new tasks: managing email credentials, recipients’ consent, and handling failures becomes your responsibility now.

◆ Coverage

1 source · 16 Oct 2026

◆ Related on Wire

◆ Topics

Developer Toolsgithubemail-notificationsactions-workflowsmtppush-events