What does "git checkout -b" do?

The command git checkout -b is a powerful and commonly used command in Git, used to create and switch to a new branch in one single operation. Here's a breakdown of what it does:

Understanding the Parts:

git checkout: This part of the command is generally used to switch between branches or restore working tree files.

-b: This option tells git checkout that, instead of simply switching to an existing branch, it should create a new branch.

Functionality:

When you run git checkout -b new_branch_name, Git performs two primary actions:

1. Creates a new branch: It creates a new branch with the name you provided (new_branch_name in this case).

2. Switches to that new branch: Immediately after creating the branch, Git switches your working directory to this newly created branch. This means that any subsequent commits you make will now be on this new branch, separate from your previous branch (often the main or master branch).

Example:

Let’s say you are on the main branch and you want to start working on a new feature. You would run:

git checkout -b feature_x

This will:

- Create a new branch named feature_x.

- Switch you to the feature_x branch so you can begin making your changes.

Why use it?

Efficiency: It combines two steps (creating a branch and switching to it) into one, which is quicker and less error-prone.

Workflow: It’s a fundamental step in the Git branching workflow. When you start a new feature, bug fix, or experiment, it's best practice to create a separate branch so your work doesn't interfere with the stable codebase in your main branch.

Important Note:

The new branch created with git checkout -b is based on the current branch where you were when you executed the command. For example, if you were on main when you ran git checkout -b feature_x, then the feature_x branch is an exact copy of the main branch at that point in time.

In summary, git checkout -b is a key command for creating and switching to a new branch in Git, streamlining the development process by separating different feature sets and making version control more efficient.

Learn more about this