Is your feature request related to a problem? Please describe:
The referee bot holds PRs whenever there's too many retests detected on a PR. However what we are seeing currently that people are manually re-triggering the lanes and then sometimes forgot to unhold the PR. This should be done by the referee as well, who should periodically take another look at the PRs it held and then unhold in case the CI is green.
Describe the solution you'd like:
Periodically query the repositories for PRs held by the bot itself, then issue an /unhold comment on the patching PRs.
Describe alternatives you've considered:
One alternative that comes to mind is a simple commenter-bot call, however that will not be able to query the detailed PR commit status. Not sure exactly whether that is ever required or if an overall "no failures" query parameters exists, need to check.
Additional context:
FYI @enp0s3 no AI, but maybe a practical solution - WDYT?
Is your feature request related to a problem? Please describe:
The referee bot holds PRs whenever there's too many retests detected on a PR. However what we are seeing currently that people are manually re-triggering the lanes and then sometimes forgot to unhold the PR. This should be done by the referee as well, who should periodically take another look at the PRs it held and then unhold in case the CI is green.
Describe the solution you'd like:
Periodically query the repositories for PRs held by the bot itself, then issue an
/unholdcomment on the patching PRs.Describe alternatives you've considered:
One alternative that comes to mind is a simple commenter-bot call, however that will not be able to query the detailed PR commit status. Not sure exactly whether that is ever required or if an overall "no failures" query parameters exists, need to check.
Additional context:
FYI @enp0s3 no AI, but maybe a practical solution - WDYT?