Introduce a new option to ensure that the subject respects certain “case” rules.

[tbouffard]

This is inspired by what is provided by @commitlint/config-conventional

In my repositories, I prefer that the subject starts by a lower case letter. This could be enforced by a rule like https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional#subject-case

Notice that @commitlint/config-conventional provides a lot of other features that we could add to this action as well. For example

• header-max-length
• subject-full-stop

What do you think about this @jef?

[jef]

I like the idea. I don't love the fact that it's nit-picky at that point (at least for me), but I do like the consistency aspect.

The important part of this action currently is using the types properly. I can see a world where we add a strict input that forces all lowercasing and maybe some other features in the future.

[tbouffard]

Thanks for your feedback and sorry for the late answer.

As an alternative configuration, we could let the user pass a regular expression to validate the “subject” part of the title.
See action-semantic-pull-request

# Configure additional validation for the subject based on a regex.
# This example ensures the subject doesn't start with an uppercase character.
subjectPattern: ^(?![A-Z]).+$