Skip to content

Commit 32aa783

Browse files
Add .asf.yaml with branch deletion protection, allow force-push
Accept ASF infrastructure branch protection ruleset but omit restrict_force_push. The Axis2 release process (release-process.md) documents `git reset --hard` + `git push --force` as the rollback path for failed `mvn release:prepare` runs, and the Maven site plugin has a known Git SCM URL bug (MSITE-1033) that can require release restarts. Deletion protection is kept. Supersedes infrastructure-ruleset-bot/default-branch-protection (#1200). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 9f8381d commit 32aa783

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

.asf.yaml

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
github:
2+
rulesets:
3+
- name: "Default Branch Protection"
4+
type: branch
5+
branches:
6+
includes:
7+
- "~DEFAULT_BRANCH"
8+
- "release/*"
9+
- "rel/*"
10+
excludes: []
11+
bypass_teams:
12+
- root
13+
restrict_deletion: true
14+
# restrict_force_push intentionally omitted — the Axis2 release
15+
# process (release-process.md) uses git reset --hard + git push
16+
# --force as the documented rollback path for mvn release:prepare
17+
# failures. The Maven site plugin also has a known bug with Git
18+
# SCM URLs (MSITE-1033) that can require release restarts.

0 commit comments

Comments
 (0)