Read a result and approve
What the Prodgator Policies check says, how a merge past a failing check is recorded, and approving a pull request in Prodgator.
Reading the result
The check run is one of:
- Success: every enforce policy approves.
- Failure: an enforce policy rejects.
- In progress (waiting): an enforce policy is still waiting on something, such as a check or an approval.
- Neutral: either every matching policy is in observe mode ("Observe mode: nothing enforced"), or no policy is bound to this repository and base branch ("No Prodgator policy applies").
The summary is a table of the policies that applied, their mode and their result. The details hold each rule's status (Pass, Fail, Waiting or Error) and reason. The Details link opens the pull request on the Pull Requests page, already expanded to its policy results.
Merged with bypass
If a pull request merges while its Prodgator Policies check is failing or still pending (an admin or a ruleset bypass actor merged it anyway), Prodgator shows Merged with bypass next to its result on the Pull Requests page, writes a entry to the audit log and sends the org a critical notification.
Prodgator names who bypassed the ruleset from GitHub's rule suites, which needs the App's Administration: Read permission. An installation without it still gets the record, the audit entry and the notification, naming the person who merged instead.
Approve in Prodgator
An or can approve or reject a pull request in Prodgator, the same way they approve a governed deployment. This never creates a GitHub review; it records the approval, which the Prodgator approvers rule counts, and updates the Prodgator Policies check.
The Prodgator approvers rule counts approvals from the users you list, from members of an approver group (Business), or from anyone whose role can approve (Release manager, Org admin, or a custom role with the approve permission) when you turn on Count an approval from anyone whose role can approve instead of naming people. By default an approval only counts on the pull request's current head commit ("Ask again after a new commit"); turn that off to let an approval carry across new commits.