potiuk opened a new pull request, #150: URL: https://github.com/apache/airflow-steward/pull/150
## Summary Replaces the existing scope-based @-mention routing in `security-issue-triage` with a history-based priority order: PR-author of the analogous prior fix → recent reviewer of the area → scope-default fallback. Caches the routing decision per code area within a bulk-mode run. ## Motivation Scope-default routing produces generic 3-person pings that the team trains itself to ignore. For airflow-s#406 (the missing `ti:self` on `task_reschedules`), the right pick was unambiguous — @amoghrajesh wrote apache/airflow#66071 introducing the mechanism, so they have the deepest context — but the scope-default rule produced a 3-person generic-providers ping. This PR codifies the priority order so the classifier reaches the same answer the human triager reaches by hand. ## Test plan - [ ] Re-run `/security-issue-triage` against airflow-s#406 and confirm the routing produces @amoghrajesh as the #1 pick (gh search of apache/airflow PRs touching `airflow_core/.../execution_api/security.py` returns PR #66071 as the most recent security-context match). - [ ] Re-run against airflow-s#404 (event-log per-DAG bypass) and confirm routing finds the PR author of #60936 (the analogous prior fix) as the #1 pick. - [ ] Confirm the cache works in bulk mode: 5 trackers all touching `airflow/api_fastapi/execution_api/` produce the same @-mention set, computed once. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
