When working on a project together, Git is a crucial tool that help teams collaborate smoothly. One of the key features is commits, which act like ...
For further actions, you may consider blocking this person and/or reporting abuse
That sounds nice, but don't get me wrong
Good amount of dev will want to push code and don't care, and above all, do not understand the importance of a well written commit message.
Most don't even know how to use git cli, again, don't care and don understand the importance of it.
Best way I've found to enforce decent commit messages was to have a semrel stage in our CI.
If messages are not compliant, there will be no builds. Hence, work is not finished.
It's not perfect, but after a few weeks devs will follow the guidelines.
Relying on a local tool for it is troubling down the road.
Eider way, this should prevent some hiccup or distraction of the dev as long he cares heheh
Yeah, there are many ways to keep devs disciplined, especially in a company.
That's a good idea, btw!
Oh~ there is a
perftag. I didn't know that. Thanks for sharing the good post!Nice, This was also my concern, that was why i created this CLI tool to do that in our projects: github.com/pshaddel/homebrew-conve...
That's good!
Thank You!
Interesting. But I'd find it more useful as a server-side pre-commit hook that rejected bad commits. Herding cats to get all the developers on the team to install this client side makes it impractical for me.
Yeah, to make
commitlintpowerful, you can use npmjs.com/package/husky.nice. thanks
Needs an option to require a gitmoji
I love me some gitmoji.
Is there anyway we can use this or any alternative linter with Gitlens in VSCode?
Yeah, there is. You can use it with husky to make it powerful