Re: New Git hooks for checking file names in commit messages

[John Yates]

On Fri, Apr 21, 2023 at 12:55 AM Jim Porter <jporterbugs@gmail.com> wrote:
>
> This also means that if you want to use a "*" for a bulleted list of
> sentences, you should do something to make it not look like a file
> entry. For example, " *" is ok.

I am not wild about this change in commit message syntax.  It clashes
with all my other uses of git.

Do you allow more than one file on a bulleted line?  If not then could
you use a whitespace check to identify most bulleted lines which do
not actually contain a file name?

Another heuristic might be to accumulate whether among all of the
files in the diffs there are any without file extensions.  If all file names
do indeed include extensions then a bulleted line without a "." foolowed
immediately by a non-whitespace character could be skipped.