Lesson09

beginner

Understanding Commit History

Goal

Read a repository's history with git log, then add to it.

This project already has a few commits. Explore them with git log, then add a changelog and find your new commit at the top of the history.

Objectives

0/2

Stage the new CHANGELOG.md. (Current objective)
Commit it, so the history has four commits. Then run git log --oneline to find yours at the top. (Not started)

Your task nowStep 1 of 2

Stage the new CHANGELOG.md.

Need help?

Reference

The full log

$ git log

commit 9c1e5b2d7a3f4e8b6c0d1a2b3c4d5e6f7a8b9c0d (HEAD -> main)
Author: GitDojo Learner <learner@gitdojo.local>
Date:   Mon Sep 28 10:02:00 2026 +0000

    Add styles

commit 4b7d2e1f0a9c8b7a6d5e4f3a2b1c0d9e8f7a6b5c
Author: GitDojo Learner <learner@gitdojo.local>
Date:   Mon Sep 28 10:01:00 2026 +0000

    Add homepage

Newest first. Each entry shows the commit's full hash, who made it, when, and its message. HEAD -> main marks where you are right now.

One line per commit

$ git log --oneline

9c1e5b2 (HEAD -> main) Add styles
4b7d2e1 Add homepage
a3f0c47 Initial commit

--oneline shows the short hash and the first line of each message. It is the quickest way to get an overview.

Preparing your workspace…

Repository Graph

Click a commit to inspect it

0 commits

Working Tree

Not a Git repository yet

No unstaged changes

Your working tree matches the staging area.

Staging Area

Files prepared for the next commit

No staged changes

Use git add to prepare files for your next commit.

Repository

Committed history

No commits yet

Use git commit to record staged changes.