Gates defaults
Set fallback promotion paths and review gate defaults.
Open Gates > Defaults for organization defaults. See approval settings for approval controls and bypassed protection for expected bypasses and automatic close on revert.
Declared promotion path
Business plan and above. Everyone can read paths; editing needs (Release managers and Org admins by default).
Set an organization path or a path for a repository. Each has 2 to 6 ordered branch steps with an optional deployment environment per branch. The repository path replaces the organization path for that repository. Repository identity includes the provider and immutable repository ID, so renaming it keeps the setting.
A release policy can carry its own path, including environment or gate steps. That path takes precedence for its rule. The repository and organization paths are the fallback when the rule has no path. With none, an enforced declared-path rule holds the gate. Compliance's check uses only the repository and organization paths.
The path sets the expected order. It does not change how Prodgator discovers the code's history. Each required branch deployment is checked against the promoted merge commit, and skipped or out-of-order steps are shown. See Promotion path.
Approval settings
Self-approval and reviewer forwarding for your organization, a gate or one deployment environment, and which one applies.
Approve deployments
The two kinds of gate on a GitHub environment, GitLab, Bitbucket and Azure DevOps approvals, approving and rejecting from Prodgator one at a time or in bulk, and what Prodgator posts to the provider.