[Aethelwulf]

Do people really look at their git commit history like this? Why?

[Snild]

Yes. To figure out what happened, and which path it took to get into my repo. Or to see how branches have diverged.

I also recommend it to git newbies, as a tool to understand the state of their repo when something has gone wrong (e.g. they did a bad merge or rebase).

[kaffekaka]

But with rebase, the history does not show what happened. It shows the changes to the code yes, but not how they came into being.

[thomasfromcdnjs]

I've been using git since the first year it came out, I've never looked at it visually.

[kaashif]

I've been using git for ~15 years and I've also never looked at it visually, except by accident. And yes, this does include working on big repos with lots of other people. Maybe we're the weird ones.

[IshKebab]

Same reason anyone visualises any data. It makes it easier and quicker to understand (unless it is a mess due to not rebasing & too fine commit granularity).

[sschueller]

The map? Sometimes it helps to get a visual queue (at least for me) but most of the time I don't need it.

[secondcoming]

I've asked this before. I think it's down to flaws in development practices elsewhere.