![]() ![]() 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. When you push the changes to your remote Bitbucket repository, those changes apply to the repository's branch.The "checkout" command can switch the currently active branch - but it can also be used to restore files. Going forward, all your Git commands apply to the branch. In this example, the feature branch is the branch.Ĭonfirm you are now working on that branch: Using the list as reference, choose the branch you want to checkout. Notice that it lists both the branches that are local and the remote branches on Bitbucket. You should see something similar to the following: Then, do the following:Ĭhange to the root of the local repository. On your local system, make sure you have a local repository cloned from the remote repository. Using Git to checkout a branch on the command lineįor the purposes of these steps, will refer to the name of your branch. Open the terminal on your local machine and change to the root directory of your repository.Īt the command line, enter the copied command from Bitbucket and press ENTER. Press the Check out button to display the appropriate check out command.Ĭopy the command (or choose Check out in Sourcetree if you'd rather use Sourcetree). In the repository's Branches, click the branch you want to checkout. If you're using Sourcetree, Bitbucket gives you a single button checkout. The Bitbucket interface gives you the basic command for checking out a branch. When you checkout a branch, you should already have a local clone of the parent repository. ![]() If you plan to use branches a lot or want to know more, we recommend you learn more by visiting a site or buying a book devoted to the DVCS you are using (Git or Mercurial). It merely provides a pointer to help you understand how Bitbucket supports branches. The information on this page is not a definitive guide for either Git or Mercurial.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |