github / github/roadmap

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

Ouverte
#1,302 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Enterprise Free GHES 3.23 Team
Langage dominant
Aucune donnée de langage
Étoiles
8.9k
Forks
1.8k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### 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.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
github
Domaine
authorization
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.