Every line of code has a history — who wrote it, when, and in which commit. git blame reveals the author behind every single line.
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.
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.
Modern alternative:
git log -p -- filename
shows full history of changes to a specific file.