Git
The version control system behind almost every modern codebase — how to actually understand what it's doing, not just memorize commands.
gitversion-controlprogrammingbeginner
Get Yaaddi on Google Play Free. Install the app, then add this course from its Course Library.
View this course's repo on GitHub → — star it, open an issue, or suggest a fix.
40decks
57main cards
195practice cards
0%with images
v1.1.5version
Card type mix
- multiple choice: 134
- true false: 77
- select blank: 65
- code fill: 18
- match pairs: 7
- order: 5
- type answer: 4
- multi select: 1
What's covered
- What Version Control Actually Solves
- Installing and Setting Up Git
- Starting a Repository
- The Three Areas: Working, Staged, Committed
- Tracking and Staging Changes
- Committing Snapshots
- Reading Your History
- Comparing Changes
- Unstaging and Discarding Changes
- Fixing Your Last Commit
- Reverting a Commit Safely
- Resetting to an Earlier Point
- What a Branch Really Is
- Creating and Switching Branches
- Merging Branches Together
- Resolving a Merge Conflict
- Rebasing Instead of Merging
- Cleaning Up History With Interactive Rebase
- Understanding Remotes
- Pushing and Pulling
- Fetch vs. Pull
- Tracking Branches
- Forks and Pull Requests
- Writing Reviewable Commits
- Common Team Branching Strategies
- .gitignore and What Not to Track
- Removing Untracked Files
- Searching Commit History
- Blaming a Line, Fairly
- Binary-Searching for a Bug
- Tagging a Release
- Stashing Work in Progress
- Cherry-Picking a Single Commit
- Rewriting History Without Breaking Everyone
- Recovering "Lost" Commits
- Common Git Mistakes and Their Fixes
- Submodules, Briefly
- Handling Large Files With Git LFS
- How Git Actually Stores Your Data
- Recap: Key Terms
Example cards
select blank
Version control tracks ___ to your files.
select blank
Every Git ___ holds the full project history.
Latest: Haiku review fixes: corrected factual errors and cards that did not match what their lesson teaches.