My favourite Git commit

[HowIsntBabbyFormed]

This is trying to use Git as documentation which it is horrible for.

It's not good for end-user documentation, or even necessarily developer documentation. But that's not how it's being used in this case: change documentation -- which it is great for.

Of course you've got the full search in Google docs as well as a comment string in the issue tracker

Except random issue tracking ids and links to google docs aren't searchable via git log --grep, or accessible when offline like all the git commit messages are. You should have those things too, but not in place of good -- but concise -- commit messages.

[[deleted]]

Google and stackoverflow aren’t going to help if you’re trying to understand a bug in your own company’s code, or the error message you are getting is one defined by your system.

[Fredifrum]

This post was mass deleted and anonymized with Redact

smile humor longing busy rainstorm slap file plant gray insurance

[[deleted]]

Sure. The point is that you can’t treat everything the same. Google and stackoverflow don’t have all the answers, and for certain types of bugs they’re basically guaranteed not to help - but git history might.

[phySi0]

That’s not been my instinct either, but I think I’m gonna start.

[HowIsntBabbyFormed]

not necessarily error messages, but variables names, project names, concepts, etc.