That's just way too verbose though. There should have been a ticket with a description of the problem. Name the branch after the ticket and jira will automatically link the ticket to the commits that fixed it.
I've encountered bad utf-8 when data is copied from excel or outlook.
I prefer the engineering details to be in the commit message and not an external issue tracking system. That system might not be accessible 3 or 5 or 10 years later.
That is true, and it might not work for Open Source development, but I don't see managers trawling through git commits to see what was done / is in progress.
I've encountered bad utf-8 when data is copied from excel or outlook.