This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git
The following commit(s) were added to refs/heads/main by this push:
new 762b943 chore(asf.yaml): route all notifications to dev-magpie@;
reaffirm Copilot disabled (#271)
762b943 is described below
commit 762b94375047cc39e716dfd84a100bee2afcf70e
Author: Jarek Potiuk <[email protected]>
AuthorDate: Mon May 25 08:40:09 2026 +0200
chore(asf.yaml): route all notifications to dev-magpie@; reaffirm Copilot
disabled (#271)
- Notifications: redirect every scheme (jobs, commits, issues,
issues_status, issues_comment, pullrequests, pullrequests_status,
pullrequests_comment, discussions) from the Airflow PMC's main
commits@ / jobs@ lists to the dedicated
[email protected] sub-list, so the Magpie effort
gets its own subscribable feed and the Airflow PMC's main lists
stop receiving framework-repo bot traffic.
- Update surrounding comments to reflect the new routing and add
[email protected] / [email protected] alongside
[email protected] as forbidden targets.
- Rewrite the copilot_code_review comment to make explicit that
the directive is the only asfyaml lever for the Copilot
integration, so enabled: false is what "disable Copilot
completely" reduces to in this config. Setting itself was
already false.
Generated-by: Claude Code (Opus 4.7)
---
.asf.yaml | 67 ++++++++++++++++++++++++++++++++++++---------------------------
1 file changed, 38 insertions(+), 29 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index f470a4c..dea0628 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -79,13 +79,17 @@ github:
- rusackas # Evan Rusackas (Superset PMC)
- russellspitzer # Russell Spitzer (Incubator PMC, Polaris PMC,
Iceberg PMC)
- # Disable the GitHub Copilot automatic-code-review ruleset on the
- # default branch. The framework's review workflow is human-driven
- # (`pr-management-code-review` skill + maintainer review), and
- # Copilot's per-PR comments duplicate / contradict that loop.
- # The explicit `enabled: false` is required to actively remove the
- # ruleset if it was ever previously configured (per the asf.yaml
- # `copilot_code_review` directive).
+ # Disable GitHub Copilot completely on this repo. The framework's
+ # review workflow is human-driven (`pr-management-code-review`
+ # skill + maintainer review) and the agent-assisted authoring loop
+ # is Claude-Code-based; Copilot's per-PR comments and code-review
+ # ruleset duplicate / contradict both. The explicit `enabled:
+ # false` is required to actively remove the Copilot automatic-
+ # code-review ruleset if it was ever previously configured (per
+ # the asf.yaml `copilot_code_review` directive); this is the only
+ # lever asfyaml exposes for the Copilot integration today, and
+ # toggling it off is what "disable Copilot completely" reduces to
+ # in this config.
copilot_code_review:
enabled: false
@@ -175,16 +179,20 @@ github:
required_signatures: false
notifications:
- # The framework is hosted under the Airflow PMC umbrella for now;
- # routing notifications to airflow.apache.org lists matches the
- # current ownership. Revisit if/when the repo moves to
- # `apache/steward` under a different PMC.
+ # The framework is hosted under the Airflow PMC umbrella for now,
+ # but all notification streams from this repo are routed to the
+ # dedicated `[email protected]` sub-list so that the
+ # Airflow PMC's main `dev@`, `commits@`, and `jobs@` lists are not
+ # polluted with framework traffic. The sub-list belongs to the
+ # nascent Magpie effort (see `MISSION.md` /
+ # `docs/board-resolution-draft.md`) and will move with the repo
+ # when it relocates to its own TLP.
#
# 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, comment, status-check
- # event) does not belong there.
+ # `[email protected]`, `[email protected]`, or
+ # `[email protected]`. Those are the Airflow PMC's main
+ # lists; every PR, issue, push, comment, and status-check event
+ # from this repo does not belong there.
#
# ASF Infra defaults any *unset* notification field to
# `dev@<project>.apache.org`, so **every documented scheme below
@@ -198,17 +206,18 @@ notifications:
# Infra adds a new scheme, set it explicitly in the same change to
# keep the dev@ default suppressed.
#
- # Why nearly everything goes to `[email protected]`:
- # that's the standard "everything-bot-events" mirror list for the
- # Airflow PMC; jobs go to `jobs@` (CI / workflow-failure mirror).
- # Both lists are public-by-design and already moderated for
- # bot-only traffic, so there is no signal-to-noise concern.
- jobs: [email protected]
- commits: [email protected]
- issues: [email protected]
- issues_status: [email protected]
- issues_comment: [email protected]
- pullrequests: [email protected]
- pullrequests_status: [email protected]
- pullrequests_comment: [email protected]
- discussions: [email protected]
+ # All ten schemes go to a single list — `dev-magpie@` — by design:
+ # the Magpie sub-list is the one place a subscriber needs to watch
+ # to follow the framework end-to-end (CI, commits, issues, PRs,
+ # discussions). When the repo gets its own TLP and the list shape
+ # diversifies (a dedicated commits@ / jobs@ under the new PMC),
+ # split the schemes across those lists then.
+ jobs: [email protected]
+ commits: [email protected]
+ issues: [email protected]
+ issues_status: [email protected]
+ issues_comment: [email protected]
+ pullrequests: [email protected]
+ pullrequests_status: [email protected]
+ pullrequests_comment: [email protected]
+ discussions: [email protected]
