+1
Just need to try and make the bot smart enough to catch the requests vs
something legit issue. I like the idea on how you have a threshold count.
Bot should also leave a good generic message as well before closing. Something
about how we are working in various repos and do not provide set in stone ETAs.
Also to monitor NPM for releases or mailing list to track vote threads.
Since the bot will only close and not lock threads, it give the user the
ability to submit a reply to the thread if the bot closed inaccurately. Not
sure if the bot should mention that though.
We already got 9 threads about Camera plugin 4.2.0 release not on NPM because
it exists in git.
> On Jul 11, 2020, at 17:49, Niklas Merz wrote:
>
> Hi everyone,
>
> I noticed quite a number issues recently that just asked for a new
> release because the tag with the new version was created for the VOTE.
>
> As I do I thought about how to automate that. I quickly created a Github
> action [1]. It's not very smart yet but it should comment on these
> issues that we are preparing a release and follow a process.
>
> You can test it out here [2]. What do you think?
>
> Regards
> Niklas
>
> [1] https://github.com/NiklasMerz/release-notify
> [2] https://github.com/NiklasMerz/release-test
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
