Luca Weiss authored 5 years ago and Alexey Minnekhanov committed 5 years ago

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.

Lines starting with "CI:", "mrhlpr.json:" and "pmaports.cfg:" are fine,
and so is having a slash in the part after the colon.

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

Martijn Braam authored 5 years ago and Oliver Smith committed 5 years ago

Together with the related mrhlpr change, this will help us to make the
commit messages in pmaports.git more consistent.

Related: https://gitlab.com/postmarketOS/mrhlpr/merge_requests/1