Chapter 4: Git Getting Started

You’ve already asked about install, config, Git vs GitHub… now we put everything together into the complete beginner-to-first-working-repo flow — the exact path most people follow when they truly start using Git for the first time in 2026.

No skipping steps. We’ll go slow, explain why each command exists, show real output examples, and build a tiny project together. By the end you’ll have:

• Git installed & configured
• Your first local repository
• Commits, status, log, diff
• A branch + merge
• Pushed everything to GitHub

Ready? Let’s begin like day 1 of a real bootcamp.

Phase 1 – Prerequisites Checklist (Do this first!)

1. Git Installed? Open terminal / Git Bash / PowerShell → run:

   Bash

   PHP

   0 1 2 3 4 5 6

   git --version

   → You should see git version 2.53.0 (or very close — that’s the current stable release as of February 2026). If not → go back to our “Git Install” lesson and install it now.

2. Identity Set? (super important — appears on every commit)

   Bash

   PHP

   0 1 2 3 4 5 6 7

   git config --global user.name "Webliance" git config --global user.email "your-real-email-you-use-for-github@gmail.com"

3. Modern defaults (2026 style — saves headaches)

   Bash

   PHP

   0 1 2 3 4 5 6 7 8

   git config --global init.defaultBranch main git config --global core.editor "code --wait"   # change to nano/vim if no VS Code git config --global alias.lg "log --oneline --graph --decorate --all"

   Quick check:

   Bash

   PHP

   0 1 2 3 4 5 6

   git config --global --list

   See your name/email + main branch default? Good!

Phase 2 – Create & Understand Your First Repository

Goal: Make a tiny “personal-notes” project.

Output you’ll see:

→ A hidden .git/ folder appeared. That’s your entire version history database — don’t delete it!

Phase 3 – The Sacred Everyday Cycle (Add → Commit → Repeat)

1. Create your first file

   (Use VS Code, Notepad, whatever — or terminal:)

   Bash

   PHP

   0 1 2 3 4 5 6 7 8

   echo "# My Personal Notes 2026" > README.md echo "- Learn Git properly" >> README.md echo "- Drink chai every day" >> README.md

2. See what’s happening

   Bash

   PHP

   0 1 2 3 4 5 6

   git status

   Typical output:

   text

   PHP

   0 1 2 3 4 5 6 7 8 9 10 11 12 13 14

   On branch main   No commits yet   Untracked files:   (use "git add <file>..." to include in what will be committed)     README.md   nothing added to commit but untracked files present

   → Red = untracked (Git doesn’t care about it yet)

3. Stage the file (tell Git: “I want to snapshot this”)

   Bash

   PHP

   0 1 2 3 4 5 6 7

   git add README.md # or git add .   ← everything

   Bash

   PHP

   0 1 2 3 4 5 6

   git status   # now green!

   text

   PHP

   0 1 2 3 4 5 6 7 8 9 10 11 12

   On branch main   No commits yet   Changes to be committed:   (use "git rm --cached <file>..." to unstage)     new file:   README.md

   Staging area = “preparation zone” before taking photo

4. Take the photo (commit!)

   Bash

   PHP

   0 1 2 3 4 5 6

   git commit -m "Initial commit: add README with my 2026 goals"

   Output:

   text

   PHP

   0 1 2 3 4 5 6 7 8

   [main (root-commit) 1a2b3c4] Initial commit: add README with my 2026 goals 1 file changed, 3 insertions(+) create mode 100644 README.md

   → First commit done! 🎉 You now have version history.

5. See your work history

   Bash

   PHP

   0 1 2 3 4 5 6

   git log --oneline

   text

   PHP

   0 1 2 3 4 5 6

   1a2b3c4 Initial commit: add README with my 2026 goals

   Or use our alias:

   Bash

   PHP

   0 1 2 3 4 5 6

   git lg

   (Even prettier with graph when branches come)

Phase 4 – Make Changes & See Diff

Edit README.md — add one more line:

Now:

You’ll see red/green lines:

Stage & commit again:

Phase 5 – Time Travel Basics (Undo / Go Back)

Made a typo? Want to see old version?

• See what changed in last commit:

  Bash

  PHP

  0 1 2 3 4 5 6

  git show

• Go back temporarily to previous version:

  Bash

  PHP

  0 1 2 3 4 5 6

  git checkout 1a2b3c4   # use your real commit hash

  → README goes back to old version (detached HEAD warning — normal)

• Return to latest:

  Bash

  PHP

  0 1 2 3 4 5 6

  git checkout main

• Oops — want to undo last commit but keep changes?

  Bash

  PHP

  0 1 2 3 4 5 6

  git reset --soft HEAD~1

  → Changes back to staged, commit gone

• Throw away last commit completely (careful!):

  Bash

  PHP

  0 1 2 3 4 5 6

  git reset --hard HEAD~1

Phase 6 – Branches – Your Safety Net

Don’t experiment on main!

→ Now on new branch.

Add to README:

Switch back:

→ Change disappeared! (safe)

Like it? Merge:

Clean up:

Phase 7 – Push to GitHub (Make it Live!)

1. Create repo on github.com:

   • New repository → name: personal-notes-2026
   • Public / Private → no README/init files (we have our own)

2. Connect & push:

   Bash

   PHP

   0 1 2 3 4 5 6 7 8

   git remote add origin https://github.com/Webliance/personal-notes-2026.git git branch -M main git push -u origin main

   → First time may ask login (browser pops up or use PAT)

Now refresh GitHub → your commits & README are online! 🌐

Your First-Day Workflow Summary (Memorize this)

1. git status — always first!
2. Work → change files
3. git add . or specific files
4. git commit -m “clear message”
5. git push (after first setup)
6. Repeat 10–20 times → muscle memory forms

Bonus commands you’ll use daily:

• git pull → get latest from GitHub
• git clone url → copy someone else’s repo
• git branch → list branches

You did it! You’ve gone from zero to real Git + GitHub working project in one sitting.

Next class?

• Conflicts & pull requests
• .gitignore
• Real team workflow
• Or fix any error you hit during this?

Just tell me what felt tricky or what you want deeper — we’ll keep building. You’re officially “getting started” now — proud of you! 🚀