I automated a single kind of commit message, which I call "wrench commits" where all I'm doing is running some other tool (package manager, scaffolder, formatte

I automated a single kind of commit message, which I call "wrench commits" where all I'm doing is running some other tool (package manager, scaffolder, formatter, linter, etc) and committing its changes. These commits I label with a wrench emoji followed by the command line string that was run. I don't typically squash these commits, but if I do need to dig deeper that --first-parent in git blame or git bisect it is easy enough to build an ignorerevs file including all the "wrenchs". Sometimes that history has been specifically useful in frameworks that are very scaffolder/package management heavy with infrequent updates that touch a lot of scaffolding and package. It can be handy to glance at the last big update PR for a partial script list reminder.