potiuk opened a new pull request, #511: URL: https://github.com/apache/airflow-steward/pull/511
## Summary - Make the folded PR-body note the **single contributor channel** for all triage feedback (`draft`/`comment`/`close`/`ping`/`request-author-confirmation`/stale), replacing the per-action comment bodies. One compact `[!IMPORTANT]` callout, replaced in place each sweep. - **Author-only notification**: the note `@`-mentions and assigns **only** the PR author. The operator is credited and reviewers named **backtick-quoted only** — no maintainer is ever `@`-mentioned, assigned, or pinged. Reviewer-ping / reviewer-re-review variants removed. - One-line `<sub>` disclaimer replaces the multi-sentence footer. - Adds the **✅ ready-for-review flip** (replace note + un-assign author when the PR becomes ready). - Inverts the agent-guard `mention` guard: in `gh pr edit --body` it now permits the author's `@`-mention and blocks any maintainer mention. ## Motivation Promotes a local override from the Apache Airflow adopter (`.apache-magpie-overrides/pr-management-triage.md`). Maintainer mailboxes were noisy: every triage action could pile up comments and ping maintainers. Folding one replace-in-place note that pings only the author — and assigns them — makes the "your move" signal unambiguous while keeping maintainers entirely un-notified. ## Migration path - Changes the **default** behaviour under `triage_feedback_channel: pr-body`. Adopters who pin `triage_feedback_channel: comment` keep the legacy per-template comment bodies and the long footer (both retained in `comment-templates.md`). - The updated `mention` guard reaches existing adopters on their next `/magpie-setup upgrade`. ## Test plan - `prek run` on all changed files — green (lychee anchors, markdownlint, typos, placeholders, skill validator). - Applied the model live to 7 Apache Airflow contributor PRs (folded note, author assigned, operator backtick-quoted) — renders as intended. Generated-by: Claude Code (Opus 4.8) -- 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]
