Why does git clone only give me the main branch?

Cloning downloads the full repository history but only fully maps and checks out the default branch, usually main or master . Remote branches like dev exist in the repository’s history but are not registered locally until you run git fetch .

What does git fetch origin actually do?

git fetch origin downloads remote branch pointers and commits from the origin remote without modifying your working directory files. It makes your local Git installation aware of branches like origin/dev so you can switch to them.

What is the difference between git switch and git checkout -b for remote branches?

git switch dev and the older git checkout -b dev origin/dev both create a local tracking branch from the matching remote branch and move your working directory to it. git switch is the newer, more explicit command, introduced to separate branch switching from file checkout.

How do I keep uncommitted changes when switching branches?

Run git stash to temporarily shelve uncommitted changes before switching branches, then run git stash pop after switching to restore them.

I get 'error: pathspec did not match any file(s) known to git' when checking out a branch. How do I fix it?

This happens when you try to check out a remote branch before Git knows it exists locally. Run git fetch origin first, then git switch <branch> (or git checkout <branch> ).

Fixing “Landed on Main”: How to Access Remote Git Branches After Cloning

Cloning a repository is exciting — new code, new adventure. But sometimes Git drops you straight onto main when you really wanted that shiny dev branch.

      Remote (origin)          Local
    ------------------      ------------
    origin/main             main  ← default after clone
    origin/dev      ---->   dev   ← your new branch

git clone is a Git command that downloads a repository’s full history but only fully maps and checks out the default branch, usually main or master; other remote branches exist in the history but are not yet registered locally. No worries. Here’s the quick rescue plan.

How to fetch the remote branches and switch to the one you wanted follows below.

git fetch origin: Registering Remote Branches Locally

🔒 Subscribe to keep reading.

Summary: Git Fetch and Switch Workflow for Remote Branches

🔒 Subscribe to keep reading.

References

🔒 Subscribe to keep reading.

You've hit a Deep Dive tutorial.

I spend dozens of hours researching, coding, and breaking things to write these guides. This content is free, but reserved for my subscriber community. Drop your email below to unlock this guide (and all past/future deep dives):

Already a subscriber? Use the magic link from your last newsletter, or reset your password.

New subscribers get an inbox mail: Set a password to unlock articles. The form does not log you in — use the same email afterwards.

I have cloned my git repository and landed on main. How to get your branch

📚 This post is part of the "Git Survival Guide" series

Fixing “Landed on Main”: How to Access Remote Git Branches After Cloning

git fetch origin: Registering Remote Branches Locally

Git Branch Navigation Commands: switch, pull, stash Cheat Sheet

Summary: Git Fetch and Switch Workflow for Remote Branches

References

References

Citation

I have cloned my git repository and landed on main. How to get your branch

📚 This post is part of the "Git Survival Guide" series

Fixing “Landed on Main”: How to Access Remote Git Branches After Cloning

git fetch origin: Registering Remote Branches Locally

Git Branch Navigation Commands: switch, pull, stash Cheat Sheet

Summary: Git Fetch and Switch Workflow for Remote Branches

References

You're in

References

Citation