As I brought up on one such example, miss-isslington seems to be rather noisy on backport PRs. It posted no less than 17 comments (@-ing both me and the committer, which AFAIK will re-subscribe both of us even if we unsubscribe) over a three hour period, all but one or two were just either stating the status check had succeeded or that they were still in progress, and thus not really necessary/actionable.
Adding a few other events times @-ing two people (me, the author, and @storchaka , the committer) and a team auto-requested for review, times three backport PRs, one for each bugfix branch, adds up to potentially several hundred notifications. That seems likely to consume a non-trivial amount of contributor and core dev attention—a commodity in perpetually short supply.
Can the bot instead just make one comment initially when the status check passes or fails, and then only comment once on an actionable state change? This might also help with the API ratelimit issues mentioned previously, if they are still a problem.
It seems there are several open issues and at least one PR on the bot’s repo, but it doesn’t look like there was much discussion or activity on them over there, and I wanted to bring it up here to cast a wider net for feedback as to the impacts of this on others and what the desired solution is. Thanks!