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.