A quality gate is a required validation that blocks a change from advancing until it meets defined criteria. In code review, it removes routine noise so reviewers can focus on critical issues that require human judgment. section 5.4.4
Apply gates at several points in the delivery workflow:
- Place checks before, during, or after a pull request is opened or submitted. section 5.4.4
- Block merging when proposed changes fail specified quality criteria. section 5.4.4
- Automate linting, formatting, sensitive-information detection, security checks, testing, and analysis where practical. section 5.4.4
A quieter pull-request review
A pull request first passes automated checks for formatting, linting, sensitive information, and security concerns. If any check fails, merging is prevented; if they pass, the reviewer can spend more attention on high-stakes problems. section 5.4.4
Figure 5.5 Built-in GitHub precheck validates that proposed changes do not result in a conflict with the base branch and are safe to merge.
Use the GitHub precheck as a concrete example of a built-in gate that validates merge safety and detects conflicts with the base branch. section 5.4.4
