{"thread":{"id":"60415","subject":"malformed commit messages for git version 2.42.0 when \"commit.verbose true\"","startedAt":"2023-10-23T10:43:18Z","lastAt":"2023-10-23T10:43:18Z","messageCount":1,"participants":["matthieu@talbot.audio"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"483660","messageId":"9a72287d979a0bd9dce390478d8522139646fb4e@talbot.audio","threadId":"60415","inReplyTo":null,"subject":"malformed commit messages for git version 2.42.0 when \"commit.verbose true\"","fromName":"","fromEmail":"matthieu@talbot.audio","sentAt":"2023-10-23T10:36:56Z","receivedAt":"2023-10-23T10:43:18Z","isPatch":false,"sender":{"key":"matthieu@talbot.audio","avatar":null},"body":"Hello,\n\nI recently set the option `commit.verbose` to `true` for git version 2.42.0, and I really like it.\n\nHowever, most of the time, commits are malformed if I don’t remove the diff after the marker \n`# ------------------------ >8 ------------------------`\n\nI would expect that anything after the marker is automatically removed by git, or could it be that some pre-commit script see the raw commit message before it is cleaned-up by git itself?\n\nBest,\nMatthieu\n"}]}