git log: Scroll Your Project’s Timeline

You’ve been saving commits, one after another. Each one is a clean snapshot of your project. But where did they all go? And can you see them again?

Of course you can. There’s a single command that lists your entire history, newest change on top, like scrolling a social feed.

The git log command lists every commit you’ve ever made in a repository, showing each one’s ID, author, and message, with the newest commit right at the top.

What does git log actually show?

Think of an Instagram feed. The newest post sits on top. You see who posted it, and you see the caption. The git log command works the exact same way.

It shows your whole history, the full story of the project. Every commit is listed in clean, neat order, newest changes first.

So your project is not just a pile of files. It has a real timeline: what changed, who saved it, and when.

How do I read each line of git log?

Let’s read the command itself. git is the tool you call. log means “list the commits.” When you run it, each commit has three parts:

• A commit ID — a unique code that names that exact snapshot.
• An author — who saved the commit.
• A message — a short note about what changed.

Here’s what a typical entry looks like:

commit 9f2a7c1b4e8d3a6f0c5b2e1d8a4f7c9b0e3d6a2f
Author: Asha Patel <asha@example.com>
Date:   Mon Jun 9 18:42:10 2026 +0530

    Add login button to homepage

That message at the bottom is why writing clear commit messages matters. Six months later, this is the note that tells you what you did.

How do I try git log right now?

Open a terminal inside any folder where you’ve already made commits, then type:

git log

You’ll see your commits scroll by, newest on top. If the list is long, git opens it in a scrolling view. To leave that view, just press q (for “quit”). That’s the one keystroke beginners often get stuck on, so remember it.

If you’d rather see a compact version, with one commit per line, try:

git log --oneline

This is a clean way to scan your timeline at a glance.

Why does this matter for building real things?

Once you can read your history, version control stops feeling scary and starts feeling like a safety net. You can see every step you took, which makes it easy to find where something went right (or wrong).

This is the same habit professional teams use every day. And it pairs perfectly with the next skill: comparing two versions to see exactly what changed. If you’re following along from the start, it builds on the free Zero to AI Hero course, where we go from “what’s a file?” to building real apps with AI, step by step.

Key takeaways

• git log lists every commit in your repository, newest first, like scrolling a feed.
• Each entry shows three things: a commit ID (the snapshot), an author (who saved it), and a message (what changed).
• Run git log in a folder with commits to see your project’s full timeline.
• Press q to leave the scrolling view, and use git log --oneline for a compact summary.
• Your project isn’t just files — it’s a timeline you can read and trust.

Next up: Compare versions — seeing exactly what changed between commits.

---

🚀 Take the full free course: Zero to AI Hero — learn to build with AI from scratch. New lessons daily, in Hindi & English.