potiuk opened a new pull request, #282: URL: https://github.com/apache/airflow-steward/pull/282
## Summary Re-points all nine GitHub-event notification schemes in `.asf.yaml` from the dedicated `[email protected]` sub-list back to the Airflow PMC's own lists (`[email protected]` for everything except CI runs, which go to `[email protected]`). | Scheme | Before | After | |---|---|---| | `jobs` | `dev-magpie@` | `[email protected]` | | `commits` | `dev-magpie@` | `[email protected]` | | `issues` | `dev-magpie@` | `[email protected]` | | `issues_status` | `dev-magpie@` | `[email protected]` | | `issues_comment` | `dev-magpie@` | `[email protected]` | | `pullrequests` | `dev-magpie@` | `[email protected]` | | `pullrequests_status` | `dev-magpie@` | `[email protected]` | | `pullrequests_comment` | `dev-magpie@` | `[email protected]` | | `discussions` | `dev-magpie@` | `[email protected]` | ### Why Traffic volume on the Airflow PMC's lists is already strong and noisy enough that adding this repo's events does not materially change the signal/noise profile. The cost of subscribers having to follow a separate sub-list to see what was happening here turned out to outweigh the value of keeping that traffic sequestered. When the framework eventually moves to its own TLP it will inherit its own `commits@` list and the schemes will be re-pointed at that list in the same change. ### Where this differs from Airflow's own `.asf.yaml` Airflow only sets the five "main" schemes (`jobs`, `commits`, `issues`, `pullrequests`, `discussions`) explicitly and lets the four `_status` / `_comment` schemes default to `[email protected]`. This config sets all nine explicitly to `commits@` so that PR review comments, CI-status flips, and label / milestone changes land on the same list as lifecycle events instead of polluting Airflow's `dev@`. The framework's "everything on one list" principle is preserved; only the *list* changes. `commits_by_path` remains the only intentionally-unset scheme (an optional path-specific override, not a default-suppression risk). ### Cleanup No cross-references to `dev-magpie@` remain in the repo (grepped across all `.md` / `.yaml` / `.yml`; only `.asf.yaml` referenced it). Whether the `dev-magpie@` list itself stays open or is retired on the Infra side is a separate request. ## Test plan - [x] `prek run --files .asf.yaml` — yaml hooks pass (typos / trailing-whitespace / line-ending / private-key). - [ ] Post-merge: confirm the next push to `main` lands on `[email protected]` and the next CI run lands on `[email protected]`. - [ ] Post-merge: confirm `[email protected]` receives no notifications from this repo (the all-explicit routing should suppress the ASF Infra default for every scheme). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
