potiuk opened a new pull request, #491:
URL: https://github.com/apache/airflow-steward/pull/491
## Summary
- Triage maintainers reported on dev@ ("[DISCUSS] What do we do with
unreviewed PRs", 2026-06-10) that triage **comments flood their mailboxes** and
bury the real human comments on PRs they track. A PR comment notifies every
subscriber; editing the PR **description** does not.
- By default (`triage_feedback_channel: pr-body`) the deterministic
quality-violation feedback for the `draft`, `comment`, and `close` actions is
now **folded into the PR description** as an idempotent, marker-delimited
`pr-triage-fold` block (carrying `triaged=`/`head=` metadata, no `@`-mention →
fully silent) instead of posted as a comment.
- Re-triage and the `pr-management-stats` "is triaged" detection read the
block from the PR body, so folded PRs aren't re-flagged and still count as
triaged.
- Pings, author-confirmation, security-language, suspicious-changes, and
stale-sweep notices are **unchanged** — their purpose is to notify a human. A
new project-config flag defaults to the silent channel; `comment` preserves the
old behaviour.
## Type of change
- [x] Skill change (`.claude/skills/<name>/`) — :warning: no eval fixture
included yet (see Notes)
- [x] Project template (`projects/_template/`)
## Test plan
- [x] `prek run --all-files` — the touched hooks (markdownlint, typos,
doctoc, `skill-and-tool-validate`) pass (ran on commit)
- [x] Marker-token / metadata-field consistency grep across all 5 files that
read or write `pr-triage-fold`
- [x] Anchor integrity verified by `skill-and-tool-validate` (no broken
cross-file links)
- [ ] :warning: For skill *behaviour* changes: eval fixture **not** included
— flagged as follow-up below
## RFC-AI-0004 compliance
- [x] **HITL** — folding is still a maintainer-confirmed proposal; the
preview now states which channel (and whether a notification fires)
- [x] **Sandbox** — no new host access; same `gh` mutations
- [x] **Vendor neutrality** — placeholders preserved (`check-placeholders`
passes)
- [x] **Conversational + correctable** — behaviour is a
`triage_feedback_channel` project-config switch
## Linked issues
<!-- none — driven by the dev@ discussion thread -->
## Notes for reviewers
- **Default flip:** this changes the default delivery channel for existing
adopters from notifying-comment to silent body-fold. Intentional (that's the
denoise), but worth a conscious ack. Adopters can set `triage_feedback_channel:
comment` to keep the old behaviour.
- **No eval fixture yet.** A behaviour change of this size should ship a
regression eval (folded block lands + no comment; next sweep detects
`viewer_triage_fold_present` -> `already_triaged` -> skip). Happy to add it in
this PR or a follow-up — reviewer's call.
- **Design choice:** editing a contributor's PR *description* is a heavier
touch than a comment. The fold preserves the author's body and appends a
clearly-marked block below it; open to putting it at the top or fencing it
differently.
- This implements the approach **proposed on the thread** in reply to Elad —
it is not yet community-ratified, so this may warrant landing as a
visible/reviewed change rather than a silent default switch.
--
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]
