GitHub deprecates custom thread subscriptions
GitHub is removing support for custom thread subscription settings within its notification system, aiming to simplify the user experience. This change will eliminate the 'Customize' option, leaving only 'Subscribed' and 'Not subscribed' for thread-level notifications. Users currently relying on custom settings will have their existing subscriptions converted to 'Subscribed,' which may lead to an increase in notification volume. Affected users are advised to review their notification preferences and team communication patterns as the rollout progresses.
Deprecations (1) ›
- Custom Thread Subscriptions Removed
GitHub is discontinuing the ability to configure custom thread subscriptions for notifications, removing the 'Customize' option from thread-level settings. All existing custom subscriptions will automatically convert to 'Subscribed,' meaning users will receive notifications for all events in those threads. Users whose workflows depend on specific custom notification behaviors should review their settings.
https://github.blog/changelog/2026-08-10-custom-thread-subscriptions-are-being-deprecated
Related releases
- GitHub Copilot introduces Agent Plugins 1.0 for cross-client development GitHub Changelog ·
- GitHub Details Organization-Level Repository Rule Insights GitHub Changelog ·
- GitHub Enterprise Server 3.22 Release Candidate Now Available GitHub Changelog ·
- GitHub Copilot for JetBrains adds persistent memory, Ollama integration, and enterprise controls GitHub Changelog ·
- Automatically Migrate Branch Protection Rules to Repository Rulesets GitHub Changelog ·
- GitHub Copilot's MAI-Code-1-Flash model slated for deprecation GitHub Changelog ·