PR_REVIEWER_DIFF_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.

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 [email protected] or your dedicated Customer Success Manager using their email address to resolve for any queries on the same.