In the same way that you would with any normal commit, you have to add all files and push to remote to save this state. Add this version to the staging area and push to remote This will take you to the version you wanted to go back to in your local environment. ’ - You aren’t required to add this, and it may look like it has worked but if you leave this off it will take you to a new “detached head state” where you can make changes and it will allow you to make commits, but nothing will be saved and any commits you make will be lost. Use git checkout & the ID (in the same way you would checkout a branch) to go back: $ git checkout. Go back to the selected commit on your local environment Whichever option you use, take a note of the ID of the commit you want to revert to. You can also checkout your entire folder, but it is potentially a dangerous move. Committing little and often, so that your change history is clear should save you from having to take this route. git checkout: checkout a file means to see how was in a previous commit. To make a long story short: be very careful when checking out a specific commit instead of a branch (and make sure this is really what you want and need).This is useful if you didn’t give yourself useful commit messages, or you’re just not sure exactly which version you need to go back to. The consequence is that these changes can easily get lost once you check out a different revision or branch: not being recorded in the context of a branch, you lack the possibility to access that state easily. This means that when you make changes and commit them, these changes do NOT belong to any branch. When you instead choose to check out a specific commit hash, Git will NOT do this for you. Normally, when checking out a branch, Git automatically moves the HEAD pointer along when you create new commits: you're automatically and always on the newest commit of the chosen branch.
The HEAD pointer in Git determines your current working revision (and thereby the files that are placed in your project's working directory). In case you are using the Tower Git client, you can simply right-click any commit and choose "Check Out " from the contextual menu: The Detached HEAD State However, you are now also in a state called "Detached HEAD". You will then have that revision's files in your working copy. To checkout a specific commit, you can use the git checkout command and provide the revision hash as a parameter: $ git checkout 757c47d4 Maybe you want to experiment with a specific, old revision and therefore need to have that revision's files in your working copy folder. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. There are very few reasons to checkout a commit (and not a branch). In case you are using the Tower Git client, you can double-click the branch you want or (in case you have lots and lots of branches) simply use the "Quick Action" dialog to enter the branch's name, not using the mouse at all: Checking Out Commits
Any new commits you make from this point on (until you switch branches again) will be recorded in this branch's context. This branch will then be your current working branch, also referred to as "HEAD" in Git. With the git switch command (or, alternatively, the git checkout command), you can simply provide the name of the branch you want to checkout.
#Git checkout previous commit how to#
Here's how to do this: $ git switch my-branch As said, most of the time you'll want to "checkout" branches, and not individual commits. This makes branches a very safe and convenient tool in Git. The user does not have to do this manually. This also means that, if a new commit is made in that context, the branch pointer is automatically moved to that newest commit.
This means that, actually, branches don't point to a certain commit but really always to the latest commit on the corresponding branch. Branches are very practical because they are pointers to the latest commit in a certain context (it helps to think of branches simply as specific, separate contexts with names). Most of the time, you will want to checkout a branch (and not a specific revision).
0 kommentar(er)
