The git checkout command switches between branches or restores working tree files. There are a number of different options for this command that won’t be covered here, but you can take a look at all of them in the Git documentation.

Checkout a specific commit

to checkout a specific commit, run the command :

git checkout specific-commit-id

we can get the specific commit id’s by running:

git log

Checkout an Existing Branch

To checkout an existing branch, run the command:

git checkout BRANCH-NAME

Generally, Git won’t let you checkout another branch unless your working directory is clean, because you would lose any working directory changes that aren’t committed. You have three options to handle your changes: 1) trash them, 2) commit them, or 3) stash them.

Checkout a New Branch

To create and checkout out a new branch with a single command, you can use:

git checkout -b NEW-BRANCH-NAME

This will automatically switch you to the new branch.

Checkout a New Branch or Reset a Branch to a Start Point

The following command is similar to checking out a new branch, but uses the -B (note the captital B) flag and an optional START-POINT parameter:


If the BRANCH-NAME branch doesn’t exist, Git will create it and start it at START-POINT. If the BRANCH-NAME branch already exists, then Git resets the branch to START-POINT. This is equivalent to running git branch with -f.

Force a Checkout

You can pass the -f or --force option with the git checkout command to force Git to switch branches, even if you have un-staged changes (in other words, the index of the working tree differs from HEAD). Basically, it can be used to throw away local changes.

When you run the following command, Git will ignore unmerged entries:

git checkout -f BRANCH-NAME

# Alternative
git checkout --force BRANCH-NAME

Undo Changes in your Working Directory

You can use the git checkout command to undo changes you’ve made to a file in your working directory. This will revert the file back to the version in HEAD:

git checkout -- FILE-NAME