Code Review
No Change
adopt
A code review should involve both human (if possible) and machine review. Any opposition, such as unresolved comments, failed automated checks, or policy violations, should block the review from being merged. Luckily most Source Version Control (SVC) systems like GitHub, GitLab, and Gerrit have a code review process that is built into their merge process. It should be the entry point to the Continuous Integration process, and should be adopted by all teams.
Even if you are a party of 1, having machine review centralized in a standard code review process will save you a lot of headaches.
Nominclature
GitHub calls it a Pull Request, sometimes appreviated PR.
GitLab calls it a Merge Request, sometimes appreviated MR.