CHECKOUT ORIGIN MASTER GIT HOW TO

Difference between git checkout and git Clone.Difference between git checkout and git restore.Difference between git checkout and git reset.Let's go through some examples of switching branches through git checkout, and then we will touch upon the use of git switch. If it is a remote branch, it will create a tracking branch and will switch to it.If it is a local branch or an explicit remote branch, it will switch to it.Note that the command git checkout is a multi-feature command which performs multiple functions like:

CHECKOUT ORIGIN MASTER GIT HOW TO

After reading this article, you will have strong knowledge of how to switch branches in Git and what are its companion commands. We will also go through some of the similar commands of Git. Today, we will go through different use cases and examples for using git checkout and git switch. The most famous command for switching branches has always been git checkout however the newer versions of Git divided its features into specific commands. Efficient branch switching is important to safely switch from one branch and commit your changes to the desired branch. You also switch branches frequently based on priorities. If you specify 'HEAD' as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file: $ git checkout HEAD index.When working on a project, you usually work on more than one branch at a time. If, in one go, you also want to create a new local branch, you can use the '-b' parameter: $ git checkout -b new-branchīy using the '-track' parameter, you can use a remote branch as the basis for a new local branch this will also set up a 'tracking relationship' between the two: $ git checkout -b new-branch -track origin/developĪnother use case for 'checkout' is when you want to restore an old revision of a file: $ git checkout 8a7b201 index.html This will make the given branch the new HEAD branch. In its simplest (and most common) form, only the name of an existing local branch is specified: $ git checkout other-branch If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. Restores a historic revision of a given file. when unpushed commits in the local branch or unpulled commits in the remote exist). This allows you to more easily see when the two aren't in sync (i.e.

This way, the new local branch has a tracking relationship with its remote counterpart. This can be used as a shortcut instead of the following two commands:Ĭreates a new local branch - and sets up an 'upstream' configuration. b Ĭreates a new local branch and directly switches to it. By specifying the name of a local branch, you will switch to this branch and make it the current 'HEAD' branch. The name of a local branch that you want to switch to. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched. The most common use case for 'checkout' is when you want to switch to a different branch, making it the new HEAD branch.Īnother use case for 'checkout' is when you want to restore a historic version of a specific file. The 'checkout' command can switch the currently active branch - but it can also be used to restore files.

Checkout origin master git