If we cannot describe in the subject what we are doing, we should not commit it. Icons are perfect to define actions (fixing bugs, improving the layout, etc) h

If we cannot describe in the subject what we are doing, we should not commit it. Icons are perfect to define actions (fixing bugs, improving the layout, etc) however, the commit is important when you are doing releases, cherry-picks, maintaining patches, etc. I'm not against changes and sure the icons look very cool on the front page of GitHub or in `git log`. However, most of the maintainers, who actually do things with commits, they work looking at the content. Be useful in the future, to understand what was going on, is the main purpose of the commit message. I agree that a bug, a rocket (and others) can be used to improve the subject of a commit, eventually, the problems are: -by introducing icons, are we creating a perfect excuse to be lazy during the commit phase? -Will the icons makes our history of change the poorest?