How to Git Clone a Specific Branch?

For example:

git clone -b feature-login --single-branch https://github.com/example/project.git

Here, feature-login is checked out, and the clone is limited to that branch’s history.

Can You Clone a Specific Branch Without Cloning the Full Git History?

Yes. If you only need the latest version of a branch and do not need its complete commit history, you can combine –single-branch with –depth.

For example:

git clone -b development --single-branch --depth 1 https://github.com/example/project.git

The –depth 1 option creates a shallow clone containing only the latest commit from the selected branch.

This can reduce download size and speed up cloning, especially for repositories with extensive histories. However, shallow clones have limitations when working with older commits. For example, if you need to git move commit to another branch, you may need access to additional commit history before performing the required Git operations.

Therefore, consider using a full clone when you need to work extensively with previous commits or move commits between branches.

How Do You Verify the Cloned Branch?

After cloning the repository, use:

git branch

For example:

* development

You can also check the remote repository configuration:

git remote -v

To see the current branch:

git branch --show-current

The command may return:

development

How Do You Clone a Remote Branch That Is Not the Default Branch?

You can clone any existing remote branch by specifying its name:

git clone --branch feature-payment https://github.com/example/project.git

If the branch exists on the remote repository, Git checks it out after cloning.

If you receive an error such as:

fatal: Remote branch feature-payment not found in upstream origin

verify the branch name and confirm that the branch exists on the remote repository.

You can inspect available remote branches with:

git ls-remote --heads https://github.com/example/project.git

This can help verify the exact branch name before cloning.

What If You Already Cloned the Repository?

If you have already cloned the repository and want to switch to another branch, you generally do not need to clone it again.

First, fetch the remote branch information:

git fetch origin

Then switch to the branch:

git switch development

If the branch does not already exist locally, you can create a local tracking branch:

git switch --track origin/development

Older Git versions commonly use:

git checkout -b development origin/development

The git switch command is the more focused modern command for switching branches.

What Is the Best Command for Git Clone Specific Branch?

The command depends on what you need.

What to Remember

Using git clone specific branch commands allows developers to start working with a particular branch without manually switching branches after cloning.