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
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!