moz-phab should suggest reviewers if they were not provided
Categories
(Conduit :: moz-phab, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: glob, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: conduit-triaged)
If a non-WIP change is missing reviewers moz-phab should suggest a reviewer.
I wrote a Mercurial only POC a month ago which appears to do a reasonable job:
https://gist.github.com/globau/45deecabe039753c3222aceb4118abf0
It looks reviewers of the touched files or paths over the last 60 days and lists the top 5 reviewers, prioritising reviewer groups over individuals.
It's far from perfect, but it's better than nothing when the patch author has no idea where to direct a review.
Updated•6 years ago
|
Hm, so what's different to the current behavior? When I push a non-WIP patch for changes in /remote and not adding a reviewer explicitely it works just fine:
(D74635) 592842:be9d5bd2d078 Bug 1593226 - [remote] Emit Runtime.executionContextCreated and Runtime.executionContextDestroyed events also for frames.
!! Missing reviewers
Automatically submitting (as per submit.auto_submit in ~/.moz-phab-config)
Updating revision D74635:
592842:be9d5bd2d078 Bug 1593226 - [remote] Emit Runtime.executionContextCreated and Runtime.executionContextDestroyed events also for frames.
Maybe this is because we have a herald rule setup for any changes under /remote? Byron, what does your patch change? Wont' we need such herald rules anymore?
Also we have a contributor for the remote protocol who doesn't have any privileges yet, and he is not able to push a change without specifying a reviewer. Is that somewhat related or a different issue?
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #1)
Maybe this is because we have a herald rule setup for any changes under
/remote?Byronglob, what does your patch change? Wont' we need such herald rules anymore?
Thanks for raising this.
This proposal is to suggest reviewers if one was not provided when submitting the patch to Phabricator. Depending on how the herald rule is built this would either replace or supplement the reviewer list. As automatic reviewer assignment operates is inconsistent across teams we might instead have to implement this as a separate command.
Also we have a contributor for the remote protocol who doesn't have any privileges yet, and he is not able to push a change without specifying a reviewer. Is that somewhat related or a different issue?
Unrelated - moz-phab only issues a warning for missing reviewers; it isn't an fatal error.
(In reply to :glob (Byron Jones) 🎈 from comment #2)
Also we have a contributor for the remote protocol who doesn't have any privileges yet, and he is not able to push a change without specifying a reviewer. Is that somewhat related or a different issue?
Unrelated - moz-phab only issues a warning for missing reviewers; it isn't an fatal error.
Right, he clarified that with me now that it was just the output. Good to know it works.
Comment 4•4 years ago
|
||
This could be done with mots in the future (bug 1773291).
Updated•4 months ago
|
Updated•1 month ago
|
Description
•