The “automerge” label could generate better commit messages.
Example of commit messages generated by automerge:
commit c5b242f87f31286ad38991bc3868cf4cfbf2b681 Author: Ashwin Ramaswami <[firstname.lastname@example.org](mailto:email@example.com)> Commit: Miss Islington (bot) <[firstname.lastname@example.org](mailto:31488909%2Bmissemail@example.com)> Date: Sat Aug 31 10:25:35 2019 -0500 bpo-37764: Fix infinite loop when parsing unstructured email headers. (GH-15239) Fixes a case in which email._header_value_parser.get_unstructured hangs the system for some invalid headers. This covers the cases in which the header contains either: - a case without trailing whitespace - an invalid encoded word https://bugs.python.org/issue37764 This fix should also be backported to 3.7 and 3.8 https://bugs.python.org/issue37764
- very long lines: usually, commit messages are wrapped to use 80 columns maximum
- 3 empty lines then 2 empty lines, why? 1 empty line would be enough
- “https://bugs.python.org/issue37764” link is redundant with “bpo-37764:”
- “https://bugs.python.org/issue37764” link is written twice (this issue might be specific to this specific PR/change)
The bot doesn’t log who approved the PR: “Commit: Miss Islington
(bot) <firstname.lastname@example.org>” is not
helpful. I would prefer to have directly the information in Git, rather than depending on GitHub (we might migrate to yet another forge in 10 years).