[Python-Dev] GH-NNNN vs #NNNN in merge commit (original) (raw)
Mariatta Wijaya mariatta.wijaya at gmail.com
Fri Jan 26 12:22:11 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 ]
I believe https://github.com/python/bedevere/pull/82 will add a comment, which will get emailed to everyone nosy on the PR.
Yes, and I've just updated my PR description:
If a PR was merged and the commit message was not changed from #NNNN to GH-NNNN, bedevere-bot will leave a comment to remind the core dev to update it next time. For example:
@Mariatta: Please replace # with GH- in the commit message next time.
Thanks!Does that work for everyone?
Mariatta Wijaya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180126/4f568588/attachment.html>
- 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 ]