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

potiuk pushed a commit to branch asf-yaml-avoid-dev-list
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git

commit b93cd542b078e790a8b0b71026ad160a406b3f22
Author: Jarek Potiuk <[email protected]>
AuthorDate: Wed Apr 29 10:40:28 2026 +0200

    .asf.yaml: document the deliberate `[email protected]` avoidance
    
    The five notification fields below are already explicitly set, so
    ASF Infra is NOT routing any current event to
    `[email protected]`. The risk is the silent default: ASF
    Infra falls back to `dev@<project>.apache.org` for any unset
    notification field, so dropping any of these five lines (e.g. by a
    future cleanup pass) silently re-enables the dev@ default.
    
    Adds an `IMPORTANT:` block above the field list spelling out:
    
    - the dev@ avoidance is deliberate;
    - the five fields below are the complete documented notification
      surface for GitHub events per the ASF asf.yaml schema (link
      included);
    - if ASF Infra ever adds a new notification field, it must be set
      explicitly in the same change to keep the dev@ default
      suppressed.
    
    No behavioural change — just makes the intent legible to future
    editors.
    
    Generated-by: Claude Code (Claude Opus 4.7)
---
 .asf.yaml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/.asf.yaml b/.asf.yaml
index 9b8692b..46b7d6e 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -56,6 +56,19 @@ notifications:
   # routing notifications to airflow.apache.org lists matches the
   # current ownership. Revisit if/when the repo moves to
   # `apache/steward` under a different PMC.
+  #
+  # IMPORTANT: do **not** route any notification stream to
+  # `[email protected]`. The dev@ list is the project's
+  # design-and-development discussion list and noise from a security-
+  # framework repo (every PR, issue, push, discussion event) does not
+  # belong there. ASF Infra defaults any *unset* notification field
+  # to `dev@<project>.apache.org`, so every field in the documented
+  # set below MUST stay explicitly populated — dropping a line here
+  # silently re-enables that dev@ default. Per the ASF asf.yaml
+  # schema (see 
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features),
+  # the five fields below are the complete notification surface for
+  # GitHub events; if Infra adds a new field, set it explicitly the
+  # same day to keep the dev@ default suppressed.
   jobs: [email protected]
   commits: [email protected]
   issues: [email protected]

Reply via email to