GitHub 弃用自定义线程订阅，8月10日起仅保留订阅/取消订阅
Custom thread subscriptions are being deprecated
GitHub 重度用户注意：自定义线程订阅即将失效，现有订阅将自动转为全量通知，可能造成信息过载。建议在变更生效前检查并调整你的通知设置，避免错过重要变更或遭受噪音干扰。
You’ll no longer be able to configure custom thread subscriptions for GitHub notifications.
你将无法再为 GitHub 通知配置自定义线程订阅。
What’s changing
变更内容
As part of this rollout, GitHub will remove support for custom thread subscription settings.
作为此次推出的一部分，GitHub 将移除对自定义线程订阅设置的支持。
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.
如果你的工作流程依赖于自定义线程订阅行为，我们建议随着此推出的进展，审查你的通知设置和团队沟通模式。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力