How to Use Git Blame for Debugging: Simple Guide

Use git blame <file> to see who last changed each line in a file and when. This helps you identify the author and commit responsible for a bug or unexpected behavior during debugging.

Syntax

The basic syntax of git blame shows the commit, author, and timestamp for each line in a file.

• git blame <file>: Shows line-by-line details for the file.
• -L <start,end>: Limits output to specific lines.
• -p: Shows detailed porcelain format for scripting.

bash

git blame <file>
git blame -L 10,20 <file>
git blame -p <file>

Example

This example shows how to use git blame on a file named app.py to find who last changed line 15.

bash

git blame -L 15,15 app.py

Output

e3a1b2c4 (Alice 2024-05-10 14:22:33 +0000 15)     print("Debugging with git blame")

Common Pitfalls

Common mistakes when using git blame include:

• Not specifying the file, which shows too much information.
• Ignoring line ranges, making it hard to find relevant changes.
• Confusing git blame output with actual bug cause; it only shows last change, not the root cause.

Always combine git blame with reading commit messages and code context.

bash

git blame <file>
# Too much output

git blame -L 20,30 app.py
# Focused output on lines 20 to 30

Quick Reference

Command	Description
git blame	Show last change info for each line in the file
git blame -L start,end	Show blame for specific line range
git blame -p	Show detailed output for scripting
git blame -w	Ignore whitespace changes when blaming

Key Takeaways

Use git blame to find who last changed a specific line to help debug issues.

Limit output with -L to focus on relevant lines and reduce noise.

Read commit messages alongside blame output for full context.

git blame shows last change, not necessarily the bug origin.

Ignore whitespace changes with -w to avoid misleading blame results.