So you value more rushed descriptions of changes than actual changes. Nice

thank you - these are useful

This is the premise of the excellent book Your Code as a Crime Scene. The history and structure of the codebase reveals a wealth of information.

Just looking at how often a file changes without knowing how big the file is seems a bit silly. Surely it should be changes/line or something?

This is a great list of commands to quickly understand a repository. Thank you for sharing.

I'm so used to magit, it seems kind of primitive to pipe git output around like this.

Anyway, I can glean a lot of this information in a few minutes scrolling through and filtering the log in magit, and it doesn't require memorizing a bunch of command line arguments.

Step 6: grep the thread count on the squash-merge debate to determine if the team has unresolved interpersonal conflict.

blog posts are just comments that would have been torn apart if only posted on a forum, now masquerading as important universal edicts

This should be renamed to "Git commands that I run as a new hire to get metrics I'll forget on day 2".