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

kou pushed a commit to branch main
in repository 
https://gitbox.apache.org/repos/asf/arrow-flight-sql-postgresql.git


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

commit 6db3d55cc64fcd795b3b070b1b5329a3a70f1b0f
Author: The Apache Software Foundation <[email protected]>
AuthorDate: Sun May 17 19:23:12 2026 -0500

    [INFRA] Set up default rulesets for default and release branches (#215)
    
    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 b131eb0..ab1cad9 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -30,6 +30,19 @@ github:
     issues: true
     discussions: true
 
+  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]
   discussions: [email protected]

Reply via email to