github / github/roadmap

Expand the Triage role (edit issue title/body, transfer, convert) [GA]

未关闭
#1,302 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Enterprise Free GHES 3.23 Team
主要语言
没有语言数据
星标
8.9k
派生
1.8k
PR 合并指标
30 天内没有已合并 PR

描述

### Value Prop
The triage repository role now supports editing issue titles and descriptions, transferring issues between repositories, and converting issues to discussions — giving trusted contributors the tools they need to actually manage a backlog. You can bring on community triagers without handing over push access to your codebase, keeping your source code secure while still getting real help with housekeeping. This makes the triage role genuinely useful for open source maintainers and teams that rely on community contributions.

### Expected Outcome
Maintainers should be able to delegate issue and project housekeeping to trusted contributors without granting write access to source code. By closing the gap between what the triage role is named for and what it can actually do, teams can scale their issue management safely and with greater confidence. This reduces the friction of growing an open source project or a large team-managed repository.

贡献指南

打开贡献指南

调研方向

The issue names no files, tests, or entry points, so first locate the triage-role permission implementation and its related tests. Done means triage members can edit issue titles and bodies, transfer issues, and convert them to discussions without receiving source-code push access.

由索引模型根据 Issue 内容生成。

评估

技术栈
github
领域
authorization
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。