← All permissions
Repository permission·deployments:write
Deployments: Write
Tier 2 · Medium
Why Tier 2
Creates deployments, and approves or rejects pending ones where the caller is a required reviewer or the custom protection rule.
Context-dependent: the tier shown is the typical case. What the target is used for decides the real one.
- Target
- Repository
- Plane
- DataWorkflows: Workflow files and runs, variables, deployments, environments and Pages.
- Granted by
- Fine-grained PAT, GitHub App, GITHUB_TOKEN
- Available on
- Every setup
- In a workflow
permissions: deployments: write
What it unlocks
5 REST endpoints need this permission. A few of them:
- POST /repos/{owner}/{repo}/actions/runs/{run_id}/deployment_protection_rule
- POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments
- POST /repos/{owner}/{repo}/deployments
- DELETE /repos/{owner}/{repo}/deployments/{deployment_id}
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
- T0repodocumented
- T2public_repostated by GitHub
- T2repo_deploymentdocumented
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.