Add section on required reviewers in pull requests to enhance repository security

Author: Randy Pagels

learn-pr/github/maintain-secure-repository-github/includes/2-how-to-maintain-secure-repository.md

@@ -117,6 +117,26 @@ You can use the workflows that protect the branch to:
 - Run automated tests to check for any behavior changes of the code;
 - And so on.
 
+## Required reviewers in pull requests
+
+You can improve repository security by requiring reviews before code is merged into important branches. Required reviewers help enforce quality, security, and accountability.
+
+To configure required reviewers:
+
+1. Navigate to the repository on GitHub.
+2. Under the repository name, click **Settings** > **Branches**.
+3. Next to the branch you want to protect, click **Add rule** or edit an existing rule.
+4. Select **Require pull request reviews before merging**.
+5. Optionally, check:
+   - **Require review from Code Owners**
+   - **Dismiss stale pull request approvals when new commits are pushed**
+   - **Require approval from someone other than the last pusher**
+
+Required reviews can’t be bypassed without admin permissions. They ensure that proposed changes are reviewed by another contributor or designated code owner before being merged.
+
+For more details, see [About protected branches](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches).
+
+
 ## Add a CODEOWNERS file
 
 By adding a [CODEOWNERS](https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-syntax) file to your repository, you can assign individual team members or entire teams as code owners to paths in your repository. These code owners are then required for pull-request reviews on any changes to files in a path for which they're configured.