Git history plays a critical role in code forensics, particularly in large code bases (or places where you may have a large number of potential authors). I. E. 10 commits just went to production from 3 different teams on one service. Something breaks a few hours later; was it one of the 10? Was it a corner case in something much older? Or was it someone's feature flag going live?
If you deal with a service that has been matiained for a few years, this is also an excellent way to figure out what was done why and when. Or figure out if a well meaning rebase accidentally clobbered a critical piece of ancient logic. Or determine who the heck owns something when you realize it's time to split up a larger service.
The list goes on. Note git history plays directly into git blame too; it can be an excellent tool in the right circumstances.
If you deal with a service that has been matiained for a few years, this is also an excellent way to figure out what was done why and when. Or figure out if a well meaning rebase accidentally clobbered a critical piece of ancient logic. Or determine who the heck owns something when you realize it's time to split up a larger service.
The list goes on. Note git history plays directly into git blame too; it can be an excellent tool in the right circumstances.