跳到主内容
精选85GitHub Changelog云与平台

GitHub 弃用自定义线程订阅,8月10日起仅保留订阅/取消订阅

Custom thread subscriptions are being deprecated

原文
推荐理由

GitHub 重度用户注意:自定义线程订阅即将失效,现有订阅将自动转为全量通知,可能造成信息过载。建议在变更生效前检查并调整你的通知设置,避免错过重要变更或遭受噪音干扰。

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.

更进一步:量化金融体系

看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力

进入量化体系 →

相似阅读

另一事件,读法相近