Command Palette

Search for a command to run...

Hectal
Phase 1Beginner2 of 9 in Git

Everyday Git

Stage precisely, read history fluently, and undo mistakes with the right command instead of the scary one.

Phase 0 gave you the model underneath Git. This phase is the 90% of commands you'll actually type every single day: staging exactly what you mean to, reading history to understand what happened, undoing mistakes with the correct tool for the situation, and keeping files out of Git that never belonged there in the first place.

0/4 · 0%
4 topics ~56 min 6 code blocks & diagrams
Start with the first topic
1
1.1

Staging & Committing Precisely

git add doesn't have to mean 'the whole file' — git add -p lets you stage individual chunks of a change, and git diff shows you exactly what you're about to commit before you commit it.

14 min 1 code practice

2
1.2

Viewing History: log, show, and blame

git log, git show, and git blame are the three tools for answering 'what happened here, when, and why' — genuinely essential for understanding any codebase you didn't write entirely yourself.

14 min 1 code practice

3
1.3

Undoing Things Safely: restore vs revert vs reset

Git has several different 'undo' commands that operate on completely different things — restore (working directory/staging), revert (public history), and reset (local history) — and picking the wrong one is the single most common way people accidentally lose work.

14 min 1 diagram 1 code practice

4
1.4

.gitignore & Ignoring Files Properly

A .gitignore file tells Git which files to never track in the first place — genuinely essential for keeping build output, dependencies, and secrets out of a repository from day one.

14 min 2 code practice