In this lesson, you will learn how to use git show to inspect the full contents, metadata, and specific code changes of any past commit in your project’s history.
Why use git show?
While git log helps you find a commit’s hash (the unique identifier), it only gives you a high-level summary. Sometimes you need to know exactly what changed and why. Instead of jumping between different commands to see the author, the date, and the code diffs, git show acts as an "all-in-one" magnifying glass for a single historical point.
How it works
When you run git show <commit-hash>, Git provides a detailed report:
- Metadata: The author's name, their email address, and the exact date the change was made.
- Commit Message: The full description explaining the intent behind the modification.
- The Patch: The actual lines of code added (prefixed with
+) or removed (prefixed with-).
For example, if you see a confusing bug in your current project, you can find the culprit commit hash via git log and then run:
git show a1b2c3d
Git will output:
commit a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0
Author: Jane Developer <jane@example.com>
Date: Mon Oct 23 10:00:00 2023 -0400
Refactor login validation logic
diff --git a/auth.py b/auth.py
index 8e3f2a1..9d4c1b2 100644
--- a/auth.py
+++ b/auth.py
@@ -10,4 +10,4 @@
- if len(password) < 5:
+ if len(password) < 8:
Analyzing Evolution
By reviewing these patches, you aren't just looking at the code; you are looking at the evolution of your project. You can see how requirements shifted over time—like changing a password length from 5 to 8 characters in the example above. This context is invaluable for debugging and understanding the reasoning behind the architecture you are working with today.
Key Takeaway: Use git show <commit-hash> to retrieve the complete history, authorship, and exact code changes of any past commit, providing the full context needed to understand your project's evolution.