Official product documentation

Deployments and environments

Published by GitHub Docs.

Published
Publication date unavailable
Accessed
26 September 2026
Read the original source

Evidence

What this source supports

  1. GitHub environments can require reviewers, restrict deployment sources, hold secrets until approval, and apply protection rules; one listed reviewer can approve, self-review can be restricted, and administrators can bypass by default.

    Locator
    Required reviewers: lines 40–48; deployment branches and tags: lines 56–75; environment secrets and approval: lines 96–102
    Editorial note
    On Free, Pro, and Team, reviewer gates apply only to public repositories. These gates cover software deployment and do not verify commercial, legal, support, data, or communications readiness.

Source handling

Link and citation record

Copyright GitHub. Linked and paraphrased only. Repository plans and protection-rule availability can change.