This is an automated email from the ASF dual-hosted git repository.

JingsongLi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git


The following commit(s) were added to refs/heads/master by this push:
     new f4dc16354b [INFRA] Set up default rulesets for default and release 
branches (#7872)
f4dc16354b is described below

commit f4dc16354beafe3fc8dd91266acc6ef7bf64441a
Author: The Apache Software Foundation <[email protected]>
AuthorDate: Sat May 23 20:51:13 2026 -0500

    [INFRA] Set up default rulesets for default and release branches (#7872)
    
    This Pull Request enables the repository to conform with the "sane
    default security settings" of the Apache Software Foundation by
    configuring a default branch ruleset that protects the default branch
    and any release branches.
    
    Note that `~DEFAULT_BRANCH` is a GitHub symbolic link to the current
    default branch (HEAD) of the repository and does not need changing.
    If the managing project does not wish to set up these defaults, please
    close this Pull Request. Alternatively, the project may merge this Pull
    Request to apply the changes immediately.
    
    If no action is taken, this Pull Request will be automatically merged by
    the Apache Infrastructure team on **2026-06-14** (30 days from now).
    
    For any further information, please reach us on Slack or at:
    [email protected]
---
 .asf.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/.asf.yaml b/.asf.yaml
index 272ec3b0a8..c9ed181a6e 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -40,6 +40,19 @@ github:
     wiki: false
     projects: false
 
+  rulesets:
+    - name: "Default Branch Protection"
+      type: branch
+      branches:
+        includes:
+          - "~DEFAULT_BRANCH"
+          - "release/*"
+          - "rel/*"
+        excludes: []
+      bypass_teams:
+        - root
+      restrict_deletion: true
+      restrict_force_push: true
 notifications:
   commits: [email protected]
   issues: [email protected]

Reply via email to