The more you understand the inner workings of git, the more you realize all the people who pointed and laughed at GitHub for being a centralized place for everyone's git repos were right.

This is especially true now that GitHub has reached 0 nines of uptime.

I also don't like that everything became all about pull requests instead of commits. Nobody reads the commit messages these days. They might as well not be there.

If I wrote all my commit messages at work by rolling my face across the keyboard, not one person would notice.

#OldManYellsAtCloud #GetOffMyLawn

I say this because I write detailed commit messages. Then in code review, someone inevitably asks why I'm doing something a certain way. The answer to their question is invariably in one of the commit messages.
@jamie it's a graybeard thing but, if they're doing a code review, why the hell aren't they using git blame as part of it???
@elight omg Evan, I'm halfway through writing a rant about how squashed PRs make git blame useless.

@jamie Only if the squasher isn't mindful about what they're squashing and how they update the commit messages.

I'm guessing you're finding: they're not.

@elight Oh, my friend, the fact that you think they're spending time squashing their own commits on their branch and updating their commit messages is delightfully optimistic. I truly mean this. I wish I could share in your optimism.

What I mean is using GitHub's "Squash and Merge" feature. It simply glorps all the commit messages into something that reads like gruel tastes. This is an actual commit message on my company's main app's `main` branch from a PR squashed this way:

@jamie oh I didn't think they were. I was hoping.