You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@fineract.apache.org by me...@apache.org on 2026/05/13 16:16:17 UTC
(fineract) 01/01: Use ruleset for protecting important branches
This is an automated email from the ASF dual-hosted git repository.
meonkeys pushed a commit to branch protected-branch-test
in repository https://gitbox.apache.org/repos/asf/fineract.git
commit f8e67c64fe815e60ac7db60385bba2363c479e0d
Author: Adam Monsen <ha...@gmail.com>
AuthorDate: Wed May 13 08:46:05 2026 -0700
Use ruleset for protecting important branches
This is an alternative to using a protected_branches stanza, but
allows us to apply the same rules to multiple branches without
duplication.
The logical change here is that develop now also has restrict_deletion
and restrict_force_push. Branches matching release/* and maintenance/*
now gain all the listed protections.
See https://github.com/apache/infrastructure-asfyaml#rulesets .
---
.asf.yaml | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 4bffd993f9..13815dbda0 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -19,10 +19,20 @@ github:
merge: true
squash: false
rebase: false
- protected_branches:
- develop:
- required_linear_history: false
+ rulesets:
+ - name: "Branch Protection"
+ type: branch
+ branches:
+ includes:
+ - "develop"
+ - "release/*"
+ - "maintenance/*"
+ # temporary (to test protections below)
+ - "protected-branch-test"
+ restrict_deletion: true
+ restrict_force_push: true
required_signatures: true
+ required_linear_history: false
required_conversation_resolution: true
notifications:
commits: commits@fineract.apache.org