You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@magpie.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/05/25 16:31:10 UTC
[PR] chore(asf.yaml): route notifications to Airflow PMC commits@ / jobs@; retire dev-magpie@ [airflow-steward]
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 `dev-magpie@airflow.apache.org` sub-list back to
the Airflow PMC's own lists (`commits@airflow.apache.org` for
everything except CI runs, which go to `jobs@airflow.apache.org`).
| Scheme | Before | After |
|---|---|---|
| `jobs` | `dev-magpie@` | `jobs@airflow.apache.org` |
| `commits` | `dev-magpie@` | `commits@airflow.apache.org` |
| `issues` | `dev-magpie@` | `commits@airflow.apache.org` |
| `issues_status` | `dev-magpie@` | `commits@airflow.apache.org` |
| `issues_comment` | `dev-magpie@` | `commits@airflow.apache.org` |
| `pullrequests` | `dev-magpie@` | `commits@airflow.apache.org` |
| `pullrequests_status` | `dev-magpie@` | `commits@airflow.apache.org` |
| `pullrequests_comment` | `dev-magpie@` | `commits@airflow.apache.org` |
| `discussions` | `dev-magpie@` | `commits@airflow.apache.org` |
### 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
`dev@airflow.apache.org`.
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
`commits@airflow.apache.org` and the next CI run lands on
`jobs@airflow.apache.org`.
- [ ] Post-merge: confirm `dev@airflow.apache.org` 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: dev-magpie-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] chore(asf.yaml): route notifications to Airflow PMC commits@ / jobs@; retire dev-magpie@ [airflow-steward]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #282:
URL: https://github.com/apache/airflow-steward/pull/282
--
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: dev-magpie-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org