[python-committers] Auto-merge the backport PR with one core dev approval and all passing CI
Mariatta Wijaya
mariatta.wijaya at gmail.com
Mon Feb 5 09:07:16 EST 2018
More information about the python-committers mailing list
Mon Feb 5 09:07:16 EST 2018
- Previous message (by thread): [python-committers] [RELEASED] Python 3.4.8 and Python 3.5.5 are now available
- Next message (by thread): [python-committers] Auto-merge the backport PR with one core dev approval and all passing CI
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I will have some time in the next couple weeks to work on miss-islington. I'm thinking to work on this issue: https://github.com/python/miss-islington/issues/44 The idea is to have miss-islington automatically merge the backport PR, after all CI passed and after a core dev approved the PR. I think this will save us a lot of button clicks and time. Just wanted to check if everyone is pretty much +1 on this, before I start writing the code. Some notes and implicationss: - The expectation is that the commit message has already been cleaned up on the master branch - It already knows how to replace the # to GH- in the commit message - miss-islington will need write access to CPython - git log it will show miss-islington (bot) as the committer - If you still want to do the merge yourself, then just don't approve miss-islington's PR. What does everyone here think about all that? Thanks. Mariatta Wijaya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180205/fd5d5685/attachment.html>
- Previous message (by thread): [python-committers] [RELEASED] Python 3.4.8 and Python 3.5.5 are now available
- Next message (by thread): [python-committers] Auto-merge the backport PR with one core dev approval and all passing CI
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list