It wholely depends on what you are hoping to get out of the commit messages. I don't want to see the local commit history of individual developers in the commi

It wholely depends on what you are hoping to get out of the commit messages. I don't want to see the local commit history of individual developers in the commit history of any shared branches (be it mainline branches or shared development branches). What I do want to see is a history of pull request merges. I don't care how they are formatted (and this is often done automatically) but it matters that if I want to check out a historical changeset that I can. This is particularly useful when there are regression bugs that managed to slip through the QA and automated testing processes and it is unclear what caused them and when. It is nice to be able to go through the commit log and identify suspect work items, check out the commits during that time and see what they changed. How you format the commit messages isn't that import as long as your pull-requests are squashed-merged (to suppress local dev workflow commits that aren't relevant to the team) and the commit messages facilitate doing that with something that links back to a work item.