chore(asf.yaml): route notifications to Airflow PMC commits@ / jobs@; retire dev-magpie@#282
Merged
Conversation
…-magpie@ sequester The framework's commit / PR / issue / discussion traffic now lands on the Airflow PMC's own `commits@` and `jobs@` lists rather than the dedicated `dev-magpie@airflow.apache.org` sub-list set up in apache#271. Rationale: 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. Routing follows Airflow's `.asf.yaml` destinations: - `jobs` -> `jobs@airflow.apache.org` (CI run notifications) - everything else -> `commits@airflow.apache.org` The four `_status` / `_comment` schemes (`issues_status`, `issues_comment`, `pullrequests_status`, `pullrequests_comment`) are set explicitly to `commits@` here rather than left at the ASF Infra dev@ default, so PR review comments, CI-status flips, and label / milestone changes land on the same list as the lifecycle events instead of polluting `dev@airflow.apache.org`. This is where the routing differs from Airflow's own asf.yaml: Airflow accepts those events on `dev@`; the framework keeps them on `commits@` to consolidate. `commits_by_path` remains the only intentionally-unset scheme (it is an optional path-specific override, not a default-suppression risk). If ASF Infra adds a new scheme, set it explicitly in the same change to keep the `dev@` default suppressed. No cross-references to `dev-magpie@` remain in the repo (grepped across all markdown / yaml; only `.asf.yaml` referenced it). Generated-by: Claude Code (Opus 4.7)
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-points all nine GitHub-event notification schemes in
.asf.yamlfrom the dedicated
dev-magpie@airflow.apache.orgsub-list back tothe Airflow PMC's own lists (
commits@airflow.apache.orgforeverything except CI runs, which go to
jobs@airflow.apache.org).jobsdev-magpie@jobs@airflow.apache.orgcommitsdev-magpie@commits@airflow.apache.orgissuesdev-magpie@commits@airflow.apache.orgissues_statusdev-magpie@commits@airflow.apache.orgissues_commentdev-magpie@commits@airflow.apache.orgpullrequestsdev-magpie@commits@airflow.apache.orgpullrequests_statusdev-magpie@commits@airflow.apache.orgpullrequests_commentdev-magpie@commits@airflow.apache.orgdiscussionsdev-magpie@commits@airflow.apache.orgWhy
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 thatlist in the same change.
Where this differs from Airflow's own
.asf.yamlAirflow only sets the five "main" schemes (
jobs,commits,issues,pullrequests,discussions) explicitly and lets thefour
_status/_commentschemes default todev@airflow.apache.org.This config sets all nine explicitly to
commits@so that PRreview 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_pathremains the only intentionally-unset scheme (anoptional path-specific override, not a default-suppression risk).
Cleanup
No cross-references to
dev-magpie@remain in the repo (greppedacross all
.md/.yaml/.yml; only.asf.yamlreferencedit). Whether the
dev-magpie@list itself stays open or isretired on the Infra side is a separate request.
Test plan
prek run --files .asf.yaml— yaml hooks pass (typos /trailing-whitespace / line-ending / private-key).
mainlands oncommits@airflow.apache.organd the next CI run lands onjobs@airflow.apache.org.dev@airflow.apache.orgreceives nonotifications from this repo (the all-explicit routing should
suppress the ASF Infra default for every scheme).