Ask HN: Is Git commit history useful to you?

I'm curious about how everyone here uses git commit history. I only use commit history for these use-cases:

1. When I'm trying to understand the context around a change that has been made to a file. usually the whole commit provides a better context. 2. When I want to revert a change that breaks the latest release. 3. Comparing branches for rebasing/merging

Are there any other use-case that people use git commit history for?

is commit history useful in other ways?

The git history is useful to find out: * The why, who and when of some change to the code or configuration. * Looking at older variants of code to see previous attempts to know what has already been tried. * git blame and git bisect for automated troubleshooting.

1. seeing who originally wrote the file i'm working on, which can set up some expectations, eg i know a certain someone likely didn't test the code well, if at all, so i know that i'm going to spend time constraining the existing code with tests before i can even get into it properly 2. figuring out what i did today so i can fill in the absolutely pointless timesheet that i have to fill out every day, because we can't just assign hours to a trello card, no! we have to also blurb about it so someone else can gloss over it

Occasionally I have to explain in detail what the hell I've been doing all month because of some business drama with the customer or whatever. I can barely remember what I've done the last week. So when someone asks I just open the git commit history to figure it out.

same as word document with track changes enabled… you see entire document and with history exact why each piece of the document is there and when and who made it so