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. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the. In its simplest (and most common) form, only the name of an existing local branch is specified: $ git checkout other-branch git checkout-detach git checkout -detach Prepare to work on top of , by detaching HEAD at it (see 'DETACHED HEAD' section), and updating the index and the files in the working tree.If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. Now you can work with it just like any other github repo. git remote add origin URLTOMAINGITHUBREPO. You can then add the main repo as a remote origin: git remote rename origin upstream. Clone the main repo locally if not done already. To fix this, you can easily run a git pull origin , solve the.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. To do that let's first: Create a new repo at github. branch, but you dont have that commit on your local machine. 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. You can do that using the git checkout master command.) mnelson:myproject mnelson git log. This way, the new local branch has a tracking relationship with its remote counterpart. (You may need to switch branches back to the primary branch. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |