docs(branch-protection-check): adapt check description to consider re…

…quirement of require PRs to make changes It adds the new tier 2 requirement, but also specify that the "require at least 1 reviewer" will have doubled weight. Signed-off-by: Diogo Teles Sant'Anna <[email protected]>
ossf · Sep 20, 2023 · bba4a26 · bba4a26
1 parent 7a2a8df
commit bba4a26
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/docs/checks.md b/docs/checks.md
@@ -112,7 +112,8 @@ Tier 1 Requirements (3/10 points):
   - For administrators: Include administrator for review
 
 Tier 2 Requirements (6/10 points):
-  - Require at least 1 reviewer for approval before merging
+  - For administrators: Require PRs prior to make any code changes
+  - Require at least 1 reviewer for approval before merging (for administrators, this requirement weights twice than the others in this tier)
   - For administrators: Require branch to be up to date before merging
   - For administrators: Require approval of the most recent reviewable push
 

diff --git a/docs/checks/internal/checks.yaml b/docs/checks/internal/checks.yaml
@@ -201,7 +201,8 @@ checks:
         - For administrators: Include administrator for review
 
       Tier 2 Requirements (6/10 points):
-        - Require at least 1 reviewer for approval before merging
+        - For administrators: Require PRs prior to make any code changes
+        - Require at least 1 reviewer for approval before merging (for administrators, this requirement weights twice than the others in this tier)
         - For administrators: Require branch to be up to date before merging
         - For administrators: Require approval of the most recent reviewable push