Re: GitHub Label Bot Design

Thanks Cathy. As a high level concept, scripts the project depends on should be committed to the project (I say this more as a note for everyone rather than calling you out specifically :) ). Hen On Thu, Jun 14, 2018 at 9:31 PM, Yuelin Zhang wrote: > Hi Hen, > > I am not using probot. Now my

Re: GitHub Label Bot Design

Hi Hen, I am not using probot. Now my bot code is running in a AWS lambda function. I will ask my manager and my mentors about where will the bot code be committed. Thanks, Cathy On Wed, Jun 13, 2018 at 8:09 AM, Hen wrote: > Where will the bot code be committed? > > Are you using probot? > >

Re: GitHub Label Bot Design

Where will the bot code be committed? Are you using probot? On Tue, Jun 12, 2018 at 2:21 PM Marco de Abreu wrote: > Hello Cathy, > that's a great proposal. Thank you! > > A few comments from my side: > - Good idea with the alias. We should have a special email-list for > automated reports to

Re: GitHub Label Bot Design

Hello Cathy, that's a great proposal. Thank you! A few comments from my side: - Good idea with the alias. We should have a special email-list for automated reports to prevent spamming dev@. - "Create weekly email to internal team members:" -> email-list - "Part II - Label Bot - Amazon cloudwatch

Re: GitHub Label Bot Design

Sorry for the messed up url format. Please forward to this link: https://tinyurl.com/mxnetbot Thanks, Cathy On Tue, Jun 12, 2018 at 10:20 AM, Yuelin Zhang wrote: > Hi, > > Currently there are many issues on Incubator-MXNet > repo, labeling issues

GitHub Label Bot Design

Hi, Currently there are many issues on Incubator-MXNet repo, labeling issues can drive attention of contributors to specific areas. Right now, issues are all manually labelled, which is time consuming. And every time maintainers need to @ a committer