Normally, the checkout command is used to just switch branches. Since "branches" are so cheap and easy in Git, we can easily create a new branch which starts at that old revision: $ git checkout -b old-project-state 0ad5a7a6 However, there is also a "safer" way in case you'd prefer leaving your current HEAD branch untouched. If you're sure that this is what you want, everything is fine. And in case you made a mistake: simply hit CMD+Z to undo the reset and restore the removed commits! Restoring a Revision in a New Local BranchĪs said, using the reset command on your HEAD branch is a quite drastic action: it will remove any commits (on this branch) that came after the specified revision. In case you are using the Tower Git client, you can use the reset command right from a commit's contextual menu. You'll be left with a couple of changes in your working copy and can then decide what to do with them. If you use it instead of -hard, Git will keep all the changes in those "undone" commits as local modifications: $ git reset -soft 0ad5a7a6 The reset command comes with a couple of options, one of the more interesting ones being the "-soft" flag. All commits that came after this version are effectively undone your project is exactly as it was at that point in time. This will rewind your HEAD branch to the specified version. The fastest way to restore an old version is to use the "reset" command: $ git reset -hard 0ad5a7a6 Download Now for Free Returning to an Old Revision
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |