Simple usage?

[robcresswell]

I'm unsure if I'm missing something here but... how do I use this in a straightforward way to lint the most recent commit?

Something like npx @commitlint/cli HEAD~1, assuming a relevant config file is in the same directory. The local setup doc immediately starts trying to make me install more dependencies and commit hooks, which is baffling to me.

[escapedcat]

Hey Rob, this seems to work for me:

npx commitlint --from HEAD~1 --to HEAD

Does this help in your situation?
Optionally you can add --verbose to get an output even if everything is fine.

[robcresswell]

Yes! This is what I eventually figured out. I guess I was confused this wasn't higher up on the "getting started"; maybe thats just me though.

[escapedcat]

Maybe... I actually searched the issues here and couldn't find something similar :)
Most people prefer using commitlint via a hook to avoid running it each time manually I guess. At least this didn't seem to be an issue so far.
Happy to hear some more context though.

[robcresswell]

So my use case was that I wanted something simple to run in CI; so its a one liner that checks the last 10 commits currently, though I'll make that something more sensible i.e. the diff between develop and the feature branch

[escapedcat]

Got it. There's an idea to make commitlint work with github-actions.
Maybe that would cover your usecase.

[robcresswell]

Potentially; for me it was really just wanting the most basic functionality without having to setup extra things. Anyway, I've got it figured out, so I'll close the issue. Thanks for the help, and the quick responses.