Never say what you ware doing (it's obvious this commit is updating build scripts). Say why you are doing it Don’t say what you were doing, say what the commit

Never say what you ware doing (it's obvious this commit is updating build scripts). Say why you are doing it Don’t say what you were doing, say what the commit does. A good commit message completes the sentence “when merged this will …”. Adding a more detailed description on the second line including why things were done is also not bad, but I have a strong opinion that design notes do not belong in the commit log but in code comments or markdown files that are in the repo, so that they can be found more easily and updated.