This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
commit 32aa7835d4891e48fb2f431e08980e9b1498aa08 Author: Robert Lazarski <[email protected]> AuthorDate: Sun May 17 10:53:54 2026 -1000 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) <[email protected]> --- .asf.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/.asf.yaml b/.asf.yaml new file mode 100644 index 0000000000..7d36bb3331 --- /dev/null +++ b/.asf.yaml @@ -0,0 +1,18 @@ +github: + rulesets: + - name: "Default Branch Protection" + type: branch + branches: + includes: + - "~DEFAULT_BRANCH" + - "release/*" + - "rel/*" + excludes: [] + bypass_teams: + - root + restrict_deletion: true + # restrict_force_push intentionally omitted — the Axis2 release + # process (release-process.md) uses git reset --hard + git push + # --force as the documented rollback path for mvn release:prepare + # failures. The Maven site plugin also has a known bug with Git + # SCM URLs (MSITE-1033) that can require release restarts.
