Description

This allows usage of string regular expressions as value for subject-full-stop and header-full-stop rules.

Motivation and Context

We, internally, allow a range of stops. The current rule, however, allows providing one stop character which is restrictive, at least, in our use-case.

Yet, I'm not sure if it's a better fit for a plugin or the core.

Usage examples

// commitlint.config.js
module.exports = {
  rules: {
    'subject-full-stop': [2, 'always', '[\\.0-9]'],
    'header-full-stop': [2, 'always', '[\\.0-9]']
  }
};

# subject
echo "test: subject" | commitlint # fails
echo "test: subject." | commitlint # passes
echo "test: subject #42" | commitlint # passes
echo "test: subject #420" | commitlint # passes

# header
echo "header" | commitlint # fails
echo "header." | commitlint # passes
echo "header #42" | commitlint # passes
echo "header #420" | commitlint # passes

How Has This Been Tested?

By adding new test cases.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.