chore(asf.yaml): route notifications to dev-magpie@; clarify Copilot disable#271
Merged
Merged
Conversation
…ilot disabled - 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 dev-magpie@airflow.apache.org 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 commits@airflow.apache.org / jobs@airflow.apache.org alongside dev@airflow.apache.org 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)
potiuk
added a commit
that referenced
this pull request
May 25, 2026
…-magpie@ sequester (#282) 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 #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)
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
notifications:scheme todev-magpie@airflow.apache.orginstead of the Airflow PMC's maincommits@/jobs@lists, so the framework gets its owndedicated subscribable feed.
commits@andjobs@are now also called out as "do not route here", and therationale block reflects the single-list-for-everything design
choice (revisit when this repo moves to its own TLP).
copilot_code_reviewcomment to make explicit thatthe directive is the only lever asfyaml exposes for Copilot, so
enabled: falseis what "disable Copilot completely" reduces toin this config. The setting itself was already
false.Test plan
dev-magpie@airflow.apache.orgexists / is reachablebefore merge (Infra creates / approves new mailing-list
destinations).
to confirm the notification mail lands on
dev-magpie@andnot on
commits@airflow.apache.org.remains disabled in repo settings.
Generative-AI disclosure
This change was drafted with Claude Code (Opus 4.7) on the author's
machine; the author reviewed the diff before pushing.