Support `--path` option

[medikoo]

In multi-package repo, I'd like to be able to use different commitlint configurations per package. Therefore with commitlint CLI I'd like to be able to validate commits that affect a given path only.

It'll be great if --path option is supported so we can narrow the list of validated commits to one affecting a specific directory (e.g. standard-version which generates changelog by retrieving commits supports path option, with commitlint it's not possible)

[escapedcat]

Just to understand the context a bit better. You have an example of the monorepo-setup and i.e. two different configs you might want to use?

Would you have time to provide a PR if we're moving on with this?

[medikoo]

Just to understand the context a bit better. You have an example of the monorepo-setup and i.e. two different configs you might want to use?

Yes, I'd like to use different config per package, mostly to have different scopes defined per package, as I don't want the package name to be part of the scope (that'll make commit messages verbose, and too long - it'll be hard to fit 72chars on the subject).

Would you have time to provide a PR if we're moving on with this?

Possibly, but it may take me a while to deliver that

[escapedcat]

What kind of monorepo-tooling do you use?
Commitlint is using https://github.com/conventional-changelog/commitlint/blob/master/package.json#L29

These are all scope-packages available so far:

• https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-nx-scopes
• https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-rush-scopes
• https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-lerna-scopes

Not to question your use-case but to maybe add more information to this issue.
Depending on what tool you use it might be worth adding a new scope-package instead of handling completely different commitlint-configs per package. Does this make sense to you?

[medikoo]

@escapedcat I do not use any specific tooling. I simply host a package in a nested folder and would love to be able to run commitlint in the context of that folder to validate commits that cover changes just in this folder.

e..g it's very easy to achieve with standard-version which also reads commit messages and out of it generates the changelog