[Python-Dev] GH-NNNN vs #NNNN in merge commit (original) (raw)
Berker Peksağ berker.peksag at gmail.com
Thu Jan 25 13:49:32 EST 2018
- Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 25, 2018 at 9:38 PM, Mariatta Wijaya <mariatta.wijaya at 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?)
--Berker
- Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]