![]() ![]() 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. 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 Git is a version control software that helps developers. The result of these commands is shown below: Figure 6. Optionally confirm the new branch: git branch. The -b option signifies that we are creating a new branch with the provided name and checking out that branch. git branch -d Delete the specified branch. Next, create and switch to a new loginissue branch: git checkout -b loginissue. git branch Create a new branch called branch.This is synonymous with git branch -list. If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. Git checkout remote branch is a way for a programmer to access the work of a colleague or collaborator. Common Options git branch List all of the branches in your repository. 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. 1 Answer Sorted by: 0 Will the first window continue the rest of the process on the first branch, storing all results in /data on main, then switch branches on completion Yes, the process started in the first terminal will continue. 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. To switch Git branches, enter the following command: git checkout Note: Instead of type the name for the new branch.The "checkout" command can switch the currently active branch - but it can also be used to restore files. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |