potiuk opened a new issue, #78: URL: https://github.com/apache/airflow-steward/issues/78
The F5a cooldown rule today only inspects *issue-comment* objects on the PR. It does **not** check `pull_request_review` (top-level review submissions) or `pull_request_review_comment` (in-line review comments). This caused **4 PRs** in a recent session to be flagged as "ready to ping" even though a maintainer had just left review-thread feedback minutes-to-hours earlier; the operator had to manually skip each one. ### Proposed Extend F5a to also scan: - `pull_request_review` events (top-level review submissions, including their bodies). - `pull_request_review_comment` events (in-line code-review comments). The cooldown timer should restart on the most recent activity across **any** of these comment-or-review surfaces, not just issue-comments. **Why:** maintainer engagement on review threads is engagement; ignoring it produces false positives in the "ping again" classification and costs operator attention. -- 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]
