🕵️ CHAPTER · GIT BLAME
Chef You

Who Wrote
This Line?

Every line of code has a history — who wrote it, when, and in which commit. git blame reveals the author behind every single line.

Scene I

The line-by-line investigation

Chef You

A file broke in production. You need to know who changed what, and when.

git blame recipe.js annotates each line with:
• The commit hash
• The author
• The date

Click each line to reveal who's responsible.

🕵️ BLAME VIEW Click each line to reveal the author
📄 recipe.js 10 lines
Investigation complete!

🎉 Every line accounted for

Now you know exactly who wrote what. git blame isn't about finger-pointing — it's about understanding context.

Use it to: find who to ask questions, understand why code was written a certain way, and track down the commit that introduced a bug.

$ git blame recipe.js
a1b2c3d (Alice Jan 10) function bake() {
e7b2d18 (Bob Jan 12) temp = 350;
$ git blame -L 5,8 recipe.js
# blame only lines 5-8
Epilogue
Blame is forensics, not punishment.
Every line tells a story.
Find the author, find the context.

Modern alternative: git log -p -- filename shows full history of changes to a specific file.