Commits and readable history

What you will build

Create small complete commits and use history to explain change.

Understand the idea first

Create small complete commits and use history to explain change.

Build it step by step

git add content/docs
git commit -m "feat: add study progress table"
git log --oneline --decorate -5
git show --stat HEAD

1. Open the previous project and record its result.
2. Type the example and complete: Split content and styling changes into two independently meaningful commits.
3. Change one input, predict, then verify.
4. Create and repair: Do not commit node_modules, secrets, or temporary screenshots; maintain .gitignore.

Read the important lines

• Create small complete commits and use history to explain change.
• Read input, processing, and output separately.
• Verify another input and an edge case.

Common mistakes and what to check

Practice without copying

Split content and styling changes into two independently meaningful commits.

Completion check

• I produced the required visible result
• I can explain the input, processing, and output
• I tested normal, edge, and failure cases