Git Switch vs. Git Checkout: Why You Should Stop Using the "Swiss Army Knife"
Are you still using git checkout for everything?
In this video, we dive into why Git introduced git switch and git restore in version 2.23 to replace the confusing, multi-purpose "Swiss Army knife" that is git checkout.
Historically, git checkout was used for both switching branches and restoring files, which often led to confusion and accidental data loss. We’ll show you how the modern workflow separates these tasks to follow the UNIX philosophy: "Do One Thing and Do It Well".
What you’ll learn:
The Problem: Why git checkout is considered "ambiguous" and "dangerous" for uncommitted work.
The Solution: How git switch provides a safer, focused way to manage branches.
The Command Map: How to translate your old checkout habits into modern Git.
Safety Features: How git switch prevents accidental "Detached HEAD" states.
Modern Command Cheat Sheet:
Switch to a branch: git switch branch-name
Create and switch: git switch -c new-branch
Go back: git switch -
Restore a file: git restore file
Detached HEAD (Explicitly): git switch --detach commit-hash