potiuk opened a new issue, #79: URL: https://github.com/apache/airflow-steward/issues/79
When a maintainer has substantively engaged on a draft PR (review, comment, or push), the classifier should **suppress identical bot-comment proposals** that would duplicate the maintainer's engagement. ### Recent examples (manually skipped to avoid duplicates) - potiuk-drafted [apache/airflow#58149](https://github.com/apache/airflow/pull/58149) - vargacypher-drafted [apache/airflow#63260](https://github.com/apache/airflow/pull/63260) - bugraoz93-drafted [apache/airflow#64906](https://github.com/apache/airflow/pull/64906) In each case the classifier wanted to post a comment that a maintainer had already covered in spirit on the draft. ### Open questions - Define "substantive" engagement: any review? non-trivial comment (≥ N chars / not just an emoji)? approving review only? a push by the maintainer? - Should a stale (> 1 month) maintainer engagement still suppress, or expire? - Does this apply only to drafts or also to ready-for-review PRs? Related but distinct from the "skip if triager already left a similar comment" issue: that one is similarity-based; this one is "any prior maintainer engagement". -- 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]
