GitHub 10月8日：Triage角色及以上可归档PR，归档后自动关闭并禁止评论
Triage role users or higher can now archive pull requests
核心代码托管平台的行为变更，直接影响依赖 GitHub API 或手动管理 PR 的工作流。Triage 角色获得归档权是权限优化，但“归档即自动关闭且不可评论”的语义变更属于破坏性更新，建议所有使用此功能的管理员立即检查现有流程是否受影响。
Users with the triage role or higher in a repository can now archive and unarchive pull requests. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine moderation work to someone with higher permissions.
拥有仓库中 triage 角色或更高级别权限的用户现在可以归档和解归档拉取请求。此前，归档功能仅限于仓库管理员使用，这导致需要信任的 triager 将常规审核工作转交给拥有更高权限的人。
Maintainers increasingly rely on triagers to keep pull request queues healthy without granting them permission to change code. Archiving—often used for spam, duplicate, or abandoned pull requests—is a common moderation action, and restricting it to administrators created unnecessary friction for projects that delegate this work.
维护者越来越多地依赖 triager 来保持拉取请求队列的健康状态，而无需授予他们更改代码的权限。归档（通常用于处理垃圾邮件、重复或废弃的拉取请求）是一种常见的审核操作，将其限制为管理员会在委托此项工作的项目中造成不必要的摩擦。
We’ve also improved how archived pull requests become read-only. Previously, archiving would lock the pull request, but admins were still able to leave comments. Now, we’re preventing any new activity on the pull request once it’s been archived. This keeps archived pull requests read-only without granting triage users the ability to manipulate a conversation’s locked state, which requires write access.
我们还改进了已归档拉取请求变为只读的方式。此前，归档会锁定拉取请求，但管理员仍可以留下评论。现在，一旦拉取请求被归档，我们将阻止任何新活动。这使得已归档的拉取请求变为只读，同时不会赋予 triage 用户操纵对话锁定状态的能力，因为该操作需要写入权限。
With these changes:
通过这些更改：
- Users with the triage, write, maintain, or admin role can archive and unarchive pull requests.
- Archiving automatically closes the pull request and makes its conversation read-only.
- New comments, reactions, and automated comments are blocked while a pull request is archived.
- Archived pull requests are hidden from public view and remain visible to repository administrators.
- Unarchiving restores the ability to comment and react, but does not reopen the pull request.
- 拥有 triage、write、maintain 或 admin 角色的用户可以归档和解归档拉取请求。
- 归档会自动关闭拉取请求并使其对话变为只读。
- 在拉取请求处于归档状态期间，新的评论、表情反应和自动评论将被阻止。
- 已归档的拉取请求对公众隐藏，但仍对仓库管理员可见。
- 解归档会恢复评论和表情反应的能力，但不会重新打开拉取请求。
If you have any questions or feedback, drop a comment in our Community discussion.
如果您有任何问题或反馈，请在我们的社区讨论中留言。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力