> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/code-and-repository-monitors/pr-reviewer-is-different-from-author.md). # PR Reviewer is different from Author **What does it mean to have a Peer Reviewer being different from the Author?** What is a Peer Review? Code Review, also known as Peer Code Review, is the act of consciously and systematically convening with one's fellow programmers to check each other's code for mistakes and has been repeatedly shown to accelerate and streamline the process of software development like few other practices can. The same can be institutionalize on the version control system by requiring a pull request before merging and by requiring approvals before a pull request can be merged. The same can also be read up in detail [here.](https://sprinto.freshdesk.com/support/solutions/articles/72000567166-enabling-branch-protection-rules) **What does it refer to on the Sprinto dashboard?** `Any application code which gets deployed to production should be “peer reviewed” by second pair of eyes is one of the most common security and compliance requirements and accordingly peer reviews should be done for every application code change via the integration (CI) branch for repositories that you are tracking under Change Management > Integration Branches. Goes without saying, but the author of the pull/merge request and the approver of the request should be 2 different people.` `All the pull requests/merge requests that were merged WITH AN approval will show as “Passing” checks under the “Change Management > Peer Reviews” section on Sprinto. All the pull requests/merge requests that were merged WITHOUT AN approval will show as "failing" checks under the “Change Management > Peer Reviews” section on Sprinto.` `If the checks are failing, they will have to be marked as special cases with a valid reason as to why these pull/merge requests were merged without an approval. Checks can be marked as special cases by clicking on the failing check and in the resulting drawer selecting the option "mark as special case".` If you are facing troubles to do the same you reach out to the Support Team on or your dedicated Customer Success Manager using their email address to resolve for any queries on the same. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sprinto.com/monitors/code-and-repository-monitors/pr-reviewer-is-different-from-author.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.