2 ms·
The worst commit message bureaucracy is the requirement to link to a story / feat|bug|etc classification and perfect message formatting or it gets rejected. My
by steveBK123 4y ago
The worst commit message bureaucracy is the requirement to link to a story / feat|bug|etc classification and perfect message formatting or it gets rejected.
My firm went through 3 different ticket systems in 5 years, including a round trip to Jira. Teams/apps migrated to different Jira projects, repos got split apart/merged, tickets were archived, etc.
So the commit blocking requirement of having a link to the story ends up pointing to dead ends or stuff you may not have access to quite often.
This is the kind of stuff that causes senior devs to commit less often, or to have an always-open "misc" ticket to book everything to, with a copy-paste ready commit message in the proper format to pass checks.
- rvdginste 4y agoAs a team lead I insist on a link to a ticket for stuff that is related to a ticket. When moving to another ticket system, I insist either on keeping older projects on the old system, or alternatively on migrating old tickets to the new system and keeping the original references; the same way I insist on keeping history when moving from one source control system to another one. Also... why would a company go through 3 different ticket systems in 5 years? That must cost a lot and definitely is not gonna help convincing people to use it...
- steveBK123 4y agohard to imagine, but many IT orgs are poorly run!