
Already know some of this? A 2-minute test skips the lessons you know.
Take the placement testA free 11-lesson course built from Piyush Garg's 1h 51m of YouTube video. 2 days at 90 minutes a day, with study notes and a quiz in every lesson. A 2-minute placement test skips what you already know.
Taught by Piyush Garg on YouTube. Videos play in YouTube's own player, so the creator keeps every view.
Understand what a Version Control System (VCS) is, why it is needed to track code changes over time, and how it enables reverting to previous states.
Configure global Git settings (user name and email) so commits are properly attributed, and explore the Git cheat sheet for common commands.
Create a project folder, initialize it as a Git repository with `git init`, understand the hidden `.git` folder, and start tracking files using `git add`.
Use the staging area (`git add`) to prepare changes, create commits with messages (`git commit`), view history (`git log`), and inspect changes (`git show`, `git diff`, `git blame`).
Distinguish between `git reset --hard` (moves HEAD, discards history) and `git revert` (creates a new commit undoing changes) to safely undo mistakes.
Explain the need for a central 'single source of truth' server for team collaboration, differentiate Git (VCS) from GitHub (hosted Git server with UI), and set up a GitHub repository.
Link a local repository to a GitHub remote using `git remote add origin <url>`, authenticate via SSH keys, and push/pull commits to synchronize code across developers.
Understand branching as parallel tracks for isolated feature work, create and switch branches (`git branch`, `git checkout -b`), follow naming conventions (feature/, bug/), and merge completed work back into main.
Compare merge (preserves branch topology, creates merge commit) and rebase (rewrites history linearly, keeps history clean) to decide when to use each strategy.