Dear Stéfan,

Since I just did *not* do it :s ... I realize that it could/should be the responsibility of the core dev who is squashing and merging to reword, if necessary, the 'main' commit message (which, if left unchanged, ends up being the PR title) and, perhaps(?), even the secondary commit messages (corresponding to the original individual commits).

If anything, I would think that squash merges improve the situation, otherwise those 'long list[s] of items like "polish things up a bit" and "more verbose"' end up linearly in the main commit history ( which is even worse, isn't it?  Am I missing something?

Otherwise, I believe in:

* adding a line about commit messages in;
* spreading the word about good/standard commit messages whenever we get a chance, whether formally or informally (e.g.,


On Thu, Jul 29, 2021 at 9:28 PM Stefan van der Walt <> wrote:
On Thu, Jul 29, 2021, at 12:08, Alexandre de Siqueira wrote:
> some ideas on that: I liked the talk,
> maybe there's something we could use here.

This is good.  Here is the written version:

scikit-image mailing list --
To unsubscribe send an email to
Member address: