The GitHub Actions job "prek" on airflow-steward.git/triage-history-mentions has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: b068cd053ed60263ef9c5818e5bbd8426b07a466 / Jarek Potiuk <[email protected]> triage: history-based @-mention routing replaces scope-default Replaces the existing scope-based @-mention routing in security-issue-triage with a history-based priority order: 1. PR-author of the analogous prior fix (via gh search prs) 2. Recent reviewer of the area (via gh pr list reviewed-by) 3. Scope-default fallback (existing behavior, narrowed to 1 pick) The routing decision is cached per unique code area within a bulk-mode run so a 5-tracker sweep through one directory issues one set of gh search prs queries, not five. Adds an explicit routing-failure fallback: when no PR-history match exists for a code area, the skill stops and surfaces a "confirm @-mentions before posting" prompt rather than silently defaulting to a generic roster ping. Motivation: scope-default routing produces generic 3-person pings that the team trains itself to ignore. For airflow-s#406 (missing ti:self enforcement on /execution/task-reschedules) the right pick was unambiguous — @amoghrajesh wrote apache/airflow#66071 introducing the mechanism — but the existing scope-default rule produced a generic providers ping. This PR codifies the priority order so the classifier reaches the same answer the human triager reaches by hand. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> Report URL: https://github.com/apache/airflow-steward/actions/runs/25855012240 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
