Rename project to a more generic name

[gajus]

The current project name (conventional-changelog-lint) implies that this tool is designed to be used with conventional-changelog. Regardless of whether thats true or not, the tool itself has potential for broader applications.

A good name would be something like commitlint.

[marionebl]

Hey @gajus, thanks for your suggestion!

I chose the name due to the fact this tool uses conventional-commits-parser under the hood, which basically limits it to conventional-changelog semantics.

To hold true to the commitlint name this would have to be broadened quite a bit and replace conventional-commits-parser with a custom parser, possibly using natural language processing.

Most likely this is a sizeable chunk of work which I'm currently not planing to invest into this topic. Given we can muster some collaboration effort and fill the broader scope I'd rename the project.

[gajus]

To hold true to the commitlint name this would have to be broadened quite a bit and replace conventional-commits-parser with a custom parser, possibly using natural language processing.
[..]
Given we can muster some collaboration effort and fill the broader scope I'd rename the project.

Do you have specific rules in mind that you think would be required to move from the current project scope to commitlint?

It seems that you already have quite a broad coverage. Even compared to services such as https://gitcop.com/, conventional-changelog-lint implements more rules.

[marionebl]

I think this of this more as a matter of entanglement with conventional-changelog semantics than of the perceived absolute rule coverage.

Perhaps this is not as relevant as I first thought – I'd have to search for a commit convention that could not be linted with this to prove my point.

What type of convention are you testing via conventional-changelog-lint in your projects?

[gajus]

What type of convention are you testing via conventional-changelog-lint in your projects?

https://gist.github.com/gajus/b57fd0ce6cc6de09867bbc331c4ddaf0#file-conventional-changelog-lintrc-json

Basically, Angular convention minus the scopes.

[marionebl]

Thought about splitting the angular convention in distinct parts - the scopes could be one of them...

[marionebl]

Will rename to commitlint or gitlint eventually. Things to do before this:

• Document or fix linting on shallow clones #7
• Add support for ignoring 'fixup!' commits #17
• Replace array config value rather than override element(s) #18
• ENOENT: no such file or directory, open '.git/COMMIT_EDITMSG' #19

[marionebl]

Done!