Custom thread subscriptions are being deprecated
Summary
You’ll no longer be able to configure custom thread subscriptions for GitHub notifications. What’s changing As part of this rollout, GitHub will remove support for custom thread subscription settings. If… The post Custom thread subscriptions are being deprecated appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> You’ll no longer be able to configure custom thread subscriptions for GitHub notifications.
What’s changing
As part of this rollout, GitHub will remove support for custom thread subscription settings.
If you currently rely on this feature, please note that the Customize option in the thread-level notification settings will be completely removed. After this change, only Subscribed and Not subscribed options will be available for a thread.
All existing custom subscriptions will be converted to Subscribed, and users will receive notifications for all events in those threads. If this becomes too noisy, users can unsubscribe from any affected thread.
Why we’re making this change
This change simplifies your notifications experience by:
Simplifying notification behavior.
Reducing subscription complexity.
What you need to do
No immediate action is required for most users.
If your workflow depends on custom thread subscription behavior, we recommend reviewing your notification settings and team communication patterns as this rollout progresses.
The post Custom thread subscriptions are being deprecated appeared first on The GitHub Blog.
News Radar provides aggregated summaries. Full content and copyright remain with the original publisher.