Bird
Raised Fist0
Gitdevops~5 mins

Switching branches with git switch - Commands & Configuration

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
Sometimes you need to move from one version of your project to another. The git switch command helps you change branches easily, so you can work on different features or fixes without confusion.
When you want to start working on a new feature in a separate branch.
When you need to fix a bug in an older version of your project.
When you want to review or test code on a different branch.
When you accidentally made changes on the wrong branch and want to switch to the correct one.
When you want to create a new branch and switch to it immediately.
Commands
This command switches your current working branch to 'feature-login' so you can work on that feature.
Terminal
git switch feature-login
Expected OutputExpected
Switched to branch 'feature-login'
This command creates a new branch called 'feature-payment' and switches to it immediately.
Terminal
git switch -c feature-payment
Expected OutputExpected
Switched to a new branch 'feature-payment'
→
-c - Create a new branch and switch to it
Switch back to the main branch to work on the stable version of your project.
Terminal
git switch main
Expected OutputExpected
Switched to branch 'main'
Key Concept

If you remember nothing else from this pattern, remember: git switch lets you easily move between branches or create and switch to new ones in one step.

Common Mistakes
Using 'git checkout' instead of 'git switch' for changing branches.
'git checkout' works but is older and mixes switching branches with other tasks, making it confusing.
Use 'git switch' to clearly switch branches and 'git switch -c' to create and switch to a new branch.
Trying to switch branches when you have uncommitted changes that conflict.
Git will prevent switching to avoid losing your work or causing conflicts.
Commit or stash your changes before switching branches.
Summary
Use 'git switch branch-name' to move to an existing branch.
Use 'git switch -c new-branch-name' to create and switch to a new branch.
Always commit or stash changes before switching to avoid conflicts.

Practice

(1/5)
1. What does the command git switch feature do in a Git repository?
easy
A. It shows the list of all branches including 'feature'.
B. It creates a new branch named 'feature' without switching to it.
C. It changes the current branch to the branch named 'feature'.
D. It deletes the branch named 'feature'.

Solution

  1. Step 1: Understand the git switch command

    The command git switch <branch-name> is used to change the current working branch to the specified branch.

  2. Step 2: Apply to the given command

    Here, git switch feature changes the current branch to the existing branch named 'feature'.

  3. Final Answer:

    It changes the current branch to the branch named 'feature'. -> Option C

  4. Quick Check:

    git switch <branch> changes branch [OK]
Hint: Use git switch plus branch name to move branches fast [OK]
Common Mistakes:
  • Thinking git switch creates a branch without -c
  • Confusing git switch with git branch
  • Assuming git switch deletes branches
  • Believing git switch lists branches
2. Which of the following is the correct syntax to create and switch to a new branch named dev using git switch?
easy
A. git switch -c dev
B. git switch dev -c
C. git switch --new dev
D. git switch create dev

Solution

  1. Step 1: Recall the syntax for creating and switching branches

    The correct syntax to create and switch to a new branch is git switch -c <branch-name>.

  2. Step 2: Match the syntax with options

    git switch -c dev uses git switch -c dev, which is the correct form.

  3. Final Answer:

    git switch -c dev -> Option A

  4. Quick Check:

    git switch -c <branch> creates and switches [OK]
Hint: Use -c right after git switch to create and switch [OK]
Common Mistakes:
  • Placing -c after branch name
  • Using --new instead of -c
  • Typing create instead of -c
  • Omitting the -c flag
3. Given the following commands run in order:
git switch -c test
echo 'hello' > file.txt
git add file.txt
git commit -m 'Add file'
git switch main

What is the current branch and the status of file.txt after these commands?
medium
A. On branch 'main', file.txt is not present in main branch.
B. On branch 'test', file.txt is committed and present.
C. On branch 'main', file.txt is staged but not committed.
D. On branch 'test', file.txt is untracked.

Solution

  1. Step 1: Analyze branch creation and commit

    The command git switch -c test creates and switches to 'test' branch. Then file.txt is created, added, and committed on 'test'.

  2. Step 2: Switch back to main branch

    The command git switch main switches to 'main' branch. Since file.txt was committed only on 'test', it does not exist on 'main'.

  3. Final Answer:

    On branch 'main', file.txt is not present in main branch. -> Option A

  4. Quick Check:

    Switching branches changes files to that branch's state [OK]
Hint: Committed files stay only on their branch until merged [OK]
Common Mistakes:
  • Assuming committed files appear on all branches
  • Confusing staged and committed states
  • Thinking switching branches keeps uncommitted changes
  • Believing file.txt is tracked on main after switch
4. You try to run git switch feature but get the error: error: Your local changes to the following files would be overwritten by checkout:
What should you do to fix this and switch branches safely?
medium
A. Use git switch -f feature to force switch ignoring changes.
B. Commit or stash your changes before switching branches.
C. Delete the files manually and try again.
D. Run git reset --hard without saving changes.

Solution

  1. Step 1: Understand the error meaning

    The error means you have local changes that would be lost if you switch branches.

  2. Step 2: Safely save changes before switching

    You should either commit your changes or stash them to save work before switching branches.

  3. Final Answer:

    Commit or stash your changes before switching branches. -> Option B

  4. Quick Check:

    Save changes before switching to avoid overwrite errors [OK]
Hint: Commit or stash changes before switching branches [OK]
Common Mistakes:
  • Forcing switch and losing work
  • Deleting files manually causing data loss
  • Resetting hard without backup
  • Ignoring the error and expecting switch to work
5. You want to create a new branch release from main, switch to it, and keep your current uncommitted changes safe. Which sequence of commands achieves this correctly?
hard
A. git switch -c release
git stash
git stash pop
B. git commit -m 'temp'
git switch -c release
C. git switch release
git stash
git switch -c release
D. git stash
git switch -c release
git stash pop

Solution

  1. Step 1: Save uncommitted changes safely

    Use git stash to save current uncommitted changes temporarily.

  2. Step 2: Create and switch to new branch

    Run git switch -c release to create and switch to the 'release' branch.

  3. Step 3: Restore saved changes

    Use git stash pop to apply the saved changes to the new branch.

  4. Final Answer:

    git stash
    git switch -c release
    git stash pop     -> Option D

  5. Quick Check:

    Stash changes, switch branch, then pop stash [OK]
Hint: Stash changes before switching, then pop after [OK]
Common Mistakes:
  • Switching branch before stashing causing errors
  • Committing temporary changes unnecessarily
  • Forgetting to pop stash after switching
  • Trying to switch without saving changes