I mean that you don't have to be a code owner to review a PR. If code is touched you are familiar with or code is similar to some of you've submitted before than you could be a good reviewer. The bot could pick some amount of reviewers based on this.
Best Anton чт, 27 сент. 2018 г. в 17:28, Qing Lan <lanking...@live.com>: > Great work Harsh! I like your webhook design. This would allow us to do a > great more for the label bot and speed up the response time. > > -Marco: I think Anton means the "Assignees" field in issues and PRs > > Thanks, > Qing > On 9/27/18, 5:06 PM, "Marco de Abreu" <marco.g.ab...@googlemail.com.INVALID> > wrote: > > You mean like a replacement for the codeowners feature? > > Anton Chernov <mecher...@gmail.com> schrieb am Fr., 28. Sep. 2018, > 01:39: > > > As a feature request: Could we include detection and proposal of > reviewers > > to the bot as well? > > > > Anton > > > > чт, 27 сент. 2018 г. в 15:27, Harsh Patel < > harshpatel081...@gmail.com>: > > > > > Hey, > > > I'm Harsh Patel, and I am looking to contribute to MXNet. I wanted > to get > > > some feedback to improvements that could be made with the current > > structure > > > that we have for automatically labelling issues and pull requests. > I have > > > linked my proposed design structure on the bottom of this wiki > page ( > > > > > > > > > https://cwiki.apache.org/confluence/display/MXNET/Machine+Learning+Based+GitHub+Bot > > > ) > > > - it should be under 7. Overall, users will benefit from this > design > > since > > > it will allow adding, updating, and deleting of labels freely. > Label > > > creation will be faster since this model focuses on labelling an > issue as > > > soon as it is made. Another key benefit is that we minimize the > number of > > > total GitHub API calls that need to be made. Feedback would be much > > > appreciated - I would like to hear what the developers have to say! > > Thanks. > > > > > > > >
