Make a Clean First Commit

Relax. We'll talk through this in plain words — no textbook voice.

What you'll walk away with

Understand making a clean first commit without the fear factor
Get hands-on and try it yourself
Learn to spot (and smile past) the common mistakes

Review your changes, stage only the files you need, and make your first commit with a message you can actually understand later.

Let's think about it this way for a sec

A commit is a save point for your project. A good save point covers one single topic, contains files you've already checked, and has a message with a clear purpose. git add isn't a commit yet — it's just selecting which files will go into the staging area for the next commit. git diff shows unstaged changes, while git diff --staged shows what's actually going into the commit. Read the diff to make sure no passwords, tokens, debug logs, or unnecessary generated files are in there before you commit.

Connecting it to everyday life

For your first commit, stage only the source code, package manifest, lockfile, README, and .gitignore. You can use git add ., but always double-check with git status and git diff --staged afterward. Instead of writing just 'first commit,' describe the outcome, like 'feat: build quick notes app.' Once you've committed, confirm your save point with git log --oneline.

Checked which files will be staged with git status
No secrets or debug code in git diff --staged
The commit message shows the purpose of the change
Build/tests pass before committing

Let's try it together

bash

git status
git add .
git diff --staged

# Diff မှန်မှ commit လုပ်ပါ
git commit -m "feat: build quick notes app"
git log --oneline -1

You should see

You'll end up with a clean first commit containing only project files you've reviewed.

5-Minute Try-It

Stage your project and read through git diff --staged. If you find an unwanted file, unstage it first, then commit with a message that clearly states its purpose.

A Quick Word of Caution

Never treat AI output as automatically correct. Have a human read through the code and test it — and double-check secrets and user data — before you rely on it.

Easy traps

Running git add . and committing without reading the diff
Letting secrets, console logs, or build output slip in
Using vague messages like 'update' or 'fix' that don't say what actually changed

Now Try It Yourself

Stage your project and read through git diff --staged. If you find an unwanted file, unstage it first, then commit with a message that clearly states its purpose.

You'll know it worked when: You'll end up with a clean first commit containing only project files you've reviewed.