@musicmatze Yeah, I only tolerate an npm-based solution for this is because GitHub Actions completely hides it from me (and from all contributors).
I would prefer #gitlint too, so now I'm looking at options to solve
https://github.com/jorisroovers/gitlint/issues/270
in a proper way, and packaging the latest version for Gentoo ^^
@musicmatze After reviewing several tools, I currently find #commitlint the most useful for checking commit messages.
➕: flexible enough configuration that allows me to tune it to my preferences, instead of following someone else's opinions
➖: it needs npm which doesn't fit any of my projects
I use it as a GitHub Action for PRs, and locally I let vim highlight/autoformat my own commit messages.
#gitlint is pretty close too, it only misses a "subject must start uppercase" rule I care about.
#Gitlint is a #Git commit message linter.
Gitlint helps avoid common bad practices when performing Git commits, like WIP commits, lack of a message body, etc. It does this by scanning commits and checking if they meet certain bad practice rules specified by the .gitlint file in the repository. Gitlint can be easily hooked with Git and CI systems for a more fluid linting experience.
Website 🔗️: http://jorisroovers.com/gitlint/
apt 📦️: gitlint
FErki
musicmatze
skunksarebetter