From b5a903b574ee843cc6083f65291d22b505f7f8ef Mon Sep 17 00:00:00 2001 From: gearnode Date: Tue, 7 Jan 2025 19:12:56 +0100 Subject: [PATCH] Add codebase pull request review Signed-off-by: Bryan Frimin --- controls/codebase/COD-001_patch_review.md | 34 +++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 controls/codebase/COD-001_patch_review.md diff --git a/controls/codebase/COD-001_patch_review.md b/controls/codebase/COD-001_patch_review.md new file mode 100644 index 000000000..51d60f825 --- /dev/null +++ b/controls/codebase/COD-001_patch_review.md @@ -0,0 +1,34 @@ +--- +id: "COD-001" +category: "codebase" +revision-version: 1 +revision-date: "2024-01-07" +estimate-time: "15m" +frameworks: + - name: "soc2" + sections: ["CC1.4", "CC5.2", "CC8.1"] +--- + +## Purpose +Requiring pull requests and code reviews ensures higher code quality +and security by allowing multiple team members to catch bugs, +inefficiencies, and potential vulnerabilities before code is +merged. It also promotes collaboration, knowledge sharing, and +accountability within the team. This process helps prevent issues in +production and maintains adherence to coding standards. + +## Implementation + +### Github + +1. Open your GitHub repository and go to settings. +2. In "Branche"s, click "Add Rule". +3. Enter the branch name (e.g. "main") in the branch name pattern + field. +4. Enable: "Require a pull request before merging" + +## Evidence + +- Screenshot of branch protection rules configuration +- Documentation of PR review process +- Sample PR showing enforced requirements