git blame for line-by-line history - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the git blame command do?

It shows who last changed each line in a file, along with the commit details and timestamp.

beginner

How can you use git blame to see changes for a specific file?

Run git blame filename to see line-by-line history for that file.

beginner

What information does each line in git blame output include?

It includes the commit hash, author name, date, and the actual line content.

intermediate

How can git blame help when debugging?

It helps identify who introduced a change and when, making it easier to ask questions or fix bugs.

intermediate

What option can you add to git blame to ignore whitespace changes?

Use git blame -w filename to ignore whitespace-only changes in the history.

What does git blame primarily show?

A Who last modified each line of a file

B The current status of the repository

C The list of branches

D The commit log summary

git blame shows the last person who changed each line in a file.

Which command shows line-by-line history for a file named app.js?

A git blame app.js

B git log app.js

C git status app.js

D git diff app.js

git blame app.js shows who changed each line in app.js.

What extra info does git blame show besides the author?

A File size

B Branch name

C Commit hash and date

D Remote URL

It shows commit hash, author, date, and the line content.

How do you ignore whitespace changes in git blame?

A git blame --skip-whitespace

B git blame --ignore-space

C git blame --no-whitespace

D git blame -w filename

The -w option ignores whitespace-only changes.

Why is git blame useful in debugging?

A It resets the repository

B It shows who introduced each line, helping track bugs

C It merges conflicting changes

D It deletes buggy lines automatically

Knowing who changed a line helps understand and fix bugs faster.

Explain how git blame helps you understand the history of a file.

Think about how knowing who changed each line can help.

Describe the command and option to ignore whitespace changes when using git blame.

Look for a flag that starts with a dash and relates to whitespace.