Repository permission·issues:write

Issues: Write

Tier 2 · Medium

Why Tier 2

Creates and edits issues and comments. Text in issues is what prompt injection against AI agents uses.

Target: Repository
Plane: DataCollaboration: Issues, discussions, projects and issue configuration.
Granted by: Fine-grained PAT, GitHub App, GITHUB_TOKEN
Available on: Every setup
In a workflow: permissions: issues: write

37 REST endpoints need this permission. A few of them:

T0OwnerThe organization and every repository in it
T0All-repository adminEvery repository in the organization
T1WriteOne repository
T1MaintainOne repository
T1AdminOne repository
T1Collaborator on a personal repositoryOne repository owned by a personal account
T1Security managerThe organization and every repository in it(in part: Moderation on repositories they can already write to.)
T1App managerGitHub Apps owned by the organization(in part: Moderation on repositories they can already write to.)
T1All-repository writeEvery repository in the organization
T1All-repository maintainEvery repository in the organization
T2TriageOne repository
T2MemberThe organization(in part: Moderation on repositories they can already write to.)
T2ModeratorThe organization's public spaces(in part: Moderation on repositories they can already write to.)
T2All-repository triageEvery repository in the organization
T3ReadOne repository(in part: Opening and commenting on issues, not editing anyone else's.)
T3All-repository readEvery repository in the organization(in part: Opening and commenting on issues, not editing anyone else's.)

No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.