[ci] Disable master branch protection rules
Follow up on changes due to error message
Following the action plan defined in .
A lazy consensus was reached on this matter to fix CI following the action plan.
@@ -42,13 +42,13 @@ github:
# disable rebase button:
rebase: false
protected_branches:
- master:
- required_status_checks:
+# master:
+# required_status_checks:
# strict means "Require branches to be up to date before merging".
- strict: false
+# strict: false
# Contexts are the names of checks that must pass.
# See ./github/workflows/README.md for more documentation on this list.
- contexts:
+# contexts:
# - build
# - cpp-tests
# - Changed files check
@@ -79,17 +79,18 @@ github:
# - CI - System - Tiered JCloud
# - CI - System - Sql
- required_pull_request_reviews:
- dismiss_stale_reviews: false
- require_code_owner_reviews: true
- required_approving_review_count: 1
-
- # squash or rebase must be allowed in the repo for this setting to be set to true.
- required_linear_history: true
-
- required_signatures: false
+# required_pull_request_reviews:
+# dismiss_stale_reviews: false
+# require_code_owner_reviews: true
+# required_approving_review_count: 1
+#
+# # squash or rebase must be allowed in the repo for this setting to be set to true.
+# required_linear_history: true
+#
+# required_signatures: false
# The following branch protections only ensure that force pushes are not allowed
+ master: {}
branch-1.15: {}
branch-1.16: {}
branch-1.17: {}
