Hey all,
I am looking forward to moving the predictions of labels into production.
This an effort to reduce the number of issues that go unlabelled by the
community. Labelling these issues provides a better way to serve MXNet
users. Currently there are about 10 labels which we can predict with over
helpful to triage issues!, users when
> creating a
> > > new Issue could themselves tag the issues. May be we should add that to
> > the
> > > issue template?
> > >
> > > On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel >
> > > wrote:
> >
tions and any potential issues. The
forum to this best would be here:
https://github.com/apache/incubator-mxnet/issues/13163
Best,
-Harsh Patel
he model and all of us can use it in
> incubator-mxnet repo!
> >
> > Some fun fact I would like to share:
> > 1. This new bot can recommend labels and reply to people who file it!
> > 2. It response time from 5mins -> less than 20 seconds
> >
> &g
g+Based+GitHub+Bot
Best,
-Harsh
On Mon, Oct 15, 2018 at 12:54 AM Hagay Lupesko wrote:
> +1
> Thanks for the contribution!
>
> On Fri, Oct 12, 2018 at 1:41 AM kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
>
> > Awesome work! Many thanks.
> >
well
preventing potential bottlenecks that could result from GitHub.
I would like to have a webhook for this repo:
https://github.com/apache/incubator-mxnet so that this functionality will
be used and tested by the developers here. Thanks.
Best,
-Harsh Patel
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
