git: --first-parent (intermediate) anthony explains  

That thumbnail

I somehow find it a bit weird that when you do `git log --first-parent`, it shows you what you did on the primary branch but when you do `git show --first-parent`, it shows you what you did on the secondary branch. I understand that it's because it diffs the merge commit against the previous commit on the primary branch but it's a bit unintuitive imho.

The merge commits are the reason why I usually go for squash and ff merges instead of "regular" merges but this is so useful!!

Thanks for sharing! I didn’t know it worked on `git show` and it seems to be conspicuously missing from the docs.

Between using delta over less for the git pager, a better understanding of fetch, and now how to use --first-parent my git knowledge has got good in the last week. Thanks for this!

I use the git show command with the -p/--patch and --stat arguments to show difff and files changed. I dont think I've ever used it on a merge commit (so I dont know what the output would be), however you can use git show ^N for the N different parents of the merge commit

We use squash commits and it really cleans up the git log

Hello, Anthony! I've been binge-watching your "Anthony Explains" playlist, and it's been incredibly informative. I've have an idea for a video that could be of great value to a wider audience. How about creating a long video that guides viewers through the process of building a sample toy project (CL application / python package) from the ground up, emphasizing best practices, using venv, type hints, implementing linting, type checking, testing, showcasing the steps to add it to GitHub, setting up a GitHub action (for automated testing / something else), incorporating pre-commit, publishing to pypi etc.,

Real TIL is git show 😮