(original) (raw)



On Thu, 25 Jan 2018 at 10:51 Berker Peksağ <berker.peksag@gmail.com> wrote:
On Thu, Jan 25, 2018 at 9:38 PM, Mariatta Wijaya
<mariatta.wijaya@gmail.com> wrote:
\>> That would be best solution (I think it would solve
\>> https://github.com/python/miss-islington/issues/16 too) but it's more
\>> complicated than the extension idea :) I have some time work on it if
\>> you'd like to implement the mergebot idea.
\>
\>
\> +1 for the mergebot! :)
\>
\> New bot or miss-islington's new job?
\>
\> Still +1 either way, as long as other core devs are fine with it too :)

I'm not familiar with miss-islington's codebase. Can we reuse some
parts of miss-islington in the new bot? If we can, let's implement it
in miss-islington (perhaps as a new mode?)

I would assume it would just go into miss-islington, but before we get ahead of ourselves and design this we need to get consensus that people like the overall idea of using a bot to do a main commits as well.