index.md (2922B)
1 --- 2 title: "Useful and interesting Git posts" 3 date: 2024-02-11T20:00:20-08:00 4 lastmod: 2024-11-16T15:28:48-08:00 5 draft: false 6 categories: 7 - Programming 8 tags: 9 - Git 10 --- 11 12 This is just a collection of interesting (and not necessarily recent) Git 13 posts from around the web. I may update this as I find new things. 14 15 ## Introductions 16 17 [Mikkel Paulson --- Git is my buddy: Effective Git as a solo 18 developer](https://mikkel.ca/blog/git-is-my-buddy-effective-solo-developer/) 19 20 I love reading about how other people use Git, and like Mikkel I am usually 21 using it as a “solo developer”. It’s interesting how different his approach 22 is from my own. I think that’s partly due to us being in different lines of 23 work (I haven’t been paid to put anything on the web since the 1990s), but 24 it also suggests that I could be doing things better. 25 26 [Sandra Snan --- The life-changing magic of 27 git](https://idiomdrottning.org/git) 28 29 A nice introduction to Git. I really appreciate how it defines the most 30 common pieces of Git jargon. 31 32 [Nick Farina --- Git is simpler than you 33 think](https://nfarina.com/post/9868516270/git-is-simpler) 34 35 This is an older post, written at a time when many programmers were still 36 using Subversion, and it’s worth checking out for the vintage screenshots 37 alone. But it also serves as a great introduction to what Git is doing 38 under the hood. 39 40 [Julia Evans --- Inside .git](https://jvns.ca/blog/2024/01/26/inside-git/) 41 42 This comic (with accompanying text) goes even deeper into what Git is 43 actually doing. A “Git repository” is just regular directory full of source 44 code (or whatever) called the “working copy”, plus a .git directory 45 containing a collection of special files. This breaks down all those files. 46 47 ## Opinions 48 49 [Dan Kelch --- Nobody cares about your Git 50 history](https://spin.atomicobject.com/git-history/) 51 52 You can ignore the provocative title (or appreciate it), but really this is 53 good guidance on how to think about rebasing vs. merging. 54 55 [Alex Kladov --- Git 56 things](https://matklad.github.io/2023/12/31/git-things.html) 57 58 “A grab bag of less frequently talked about git adjacent points.” The stuff 59 about CI and code review is always fascinating to me---a “solo 60 developer”---a window into a whole other world of writing code for a living. 61 The tips for working on merge commits are great, and I’ve adopted Alex’s 62 advice on moving files and starting with empty commits 63 64 [Chris Beams --- How to Write a Git Commit 65 Message](https://cbea.ms/git-commit/) 66 67 I can’t endorse any of Chris’s cryptocurrency advice, but this is the best 68 post on why and how to craft commit messages. This post introduced me to the 69 [use of the imperative mood](https://cbea.ms/git-commit/#imperative) for 70 commit subjects. I.e., “a properly formed Git commit subject line should 71 always be able to complete the following sentence: ‘If applied, this commit 72 will _your subject line here_’.”