Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rename project to a more generic name

See original GitHub issue

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.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

gajuscommented, Aug 15, 2016

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.

1reaction

marioneblcommented, Aug 15, 2016

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.