# Git Adventures --- Part 2: When Git Starts Judging Your Decisions

In Part 1, everything was clean. Repository created. Project initialized. Branches created. Team motivated. That illusion lasted exactly one day. Because on Day 2, the team learned an important truth: Writing code is easy. Understanding history is hard. And Git remembers everything. Chapter 1 --- The Calm Before the Debugging Storm Amaresh notices something feels wrong after pulling updates. A feature that worked yesterday is broken. When did this happen? He opens the timeline: git log --oneline Output: a3f9c2b Add authentication flow 9d1a2e4 Fix validation issue c81be77 Initial setup Each commit shows a short hash (abbreviated commit ID) and message. When you need the full commit ID: git log Or to just grab HEAD's full ID: git rev-parse HEAD Output: a3f9c2b7d8e9f0a1b2c3d4e5f6g7h8i9 Pro tip: Use git log --oneline -n 20 to see only the last 20 commits. Saves scrolling through months of history. The gotcha: git log shows commits in reverse chronological order (newest first). If you're lo