Do we think of Git commits as diffs, snapshots, and/or histories?(jvns.ca)

168 points by soheilpro 2 years ago | 167 comments

Some Miscellaneous Git Facts(jvns.ca)

23 points by qsantos 3 years ago | 1 comments

Confusing Git Terminology(jvns.ca)

491 points by soheilpro 3 years ago | 257 comments

Julia Evans blog post explaining confusing git terms like HEAD, detached HEAD, fast-forward, and staging area, based on answers from Mastodon.

Git Branches: Intuition and Reality(jvns.ca)

347 points by tambourine_man 2 years ago | 215 comments

Julia Evans blog post comparing an intuitive mental model of git branches with how git actually represents branches internally.

Git rebase, what can go wrong(jvns.ca)

191 points by kens 3 years ago | 247 comments

Mounting Git commits as folders with NFS(jvns.ca)

161 points by chmaynard 2 years ago | 58 comments

.gitignore Isn't the only way to ignore files in Git(nelson.cloud)

553 points by FergusArgyll 4 months ago | 167 comments

A short blog post explaining three ways to ignore files in Git: .gitignore, .git/info/exclude, and the global ~/.config/git/ignore file.

How I configure my Git identities(benji.dog)

362 points by 8organicbits 1 year ago | 72 comments

A personal blog post explaining how the author uses Git's includeIf directive to manage separate Git identities and signing keys per directory.

Beej's Guide to Git(beej.us)

894 points by mixto 1 year ago | 280 comments

Landing page for Beej's Guide to Git, a free online guide to the Git version control system offered in HTML and other downloadable formats.

Show HN: Witr – Explain why a process is running on your Linux system(github.com)

436 points by pranshuparmar 10 months ago | 82 comments

GitHub repository for witr, a Linux CLI tool that traces a process, service, or port back to its origin and explains why it is running.

GitHub is investigating unauthorized access to their internal repositories(twitter.com)

527 points by splenditer 5 months ago | 289 comments

A post on X from GitHub stating it is investigating unauthorized access to its internal repositories, with no current evidence of impact to customer data.

Git commands I run before reading any code(piechowski.io)

2140 points by grepsedawk 6 months ago | 459 comments

Blog post by Ally Piechowski describing five git commands to find churn hotspots, bus factor, bug clusters, and crisis patterns before reading a codebase.