Open FrancoisBeaune opened 3 weeks ago
Supporting spaces is not possible because it would make a lot of false positives. For example:
Merge branch 'master' of github.com:facebook/react
Provide `grunt npm:test` for verifying NPM package functionality.
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
Merge branch 'rm-wrapup' of github.com:chenglou/react into rm-wrapup
Not sure to understand your example as it doesn't contain parentheses.
To be clear, all I'm suggesting is that spaces should be authorized in the scope part of the Conventional Commits prefix.
In other words, the regex for syntax highlighting Conventional Commits prefixes should be something like:
^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert|other)(\([^\)]+\))?:\s(.+)$
This works fine:
feat(Engine): Add a feature to the engine
But this doesn't (the prefix isn't rendered in bold):
feat(Hydra Delegate): Add a feature to the Hydra delegate