This regex seems to have served to be a bit more flexible than the
actual pass one, for any kind of exceptions needed. However, it
resulted in basically every MR since the introduction of the
COMMITSTYLE, and most likely before, to be caught by that regex
instead of the pass one. As we have made the pass regex more flexible
now, we can now remove this. This should help keep commit messages
more standardized. If there's a reason for a commit to be different,
then the merger can just ignore it.
In the regex [a-z-0-9] you don't need a backslash before the minus in
the middle, so remove that to bring it in line with other regexes.
In the regex [a-z\/-0-9] you do need a backslash in front of the minus
though, otherwise only the numbers 0 and 9 are allowed by the regex.
Let's use the imperative form in commit messages, as it is best
practice. I'm keeping "upstreamed", because that definitively happened
in the past when we merge a patch that deletes a pmaport.
Do not mark commit messages as NOK if the subject...
* has an uppercase letter (except for right after the colon)
* contains a dot or underscore before the colon
Pablo Correa Gómez