8/13/2023 0 Comments Git stash dropAlternatively, you can instead of HEAD~3, simply provide the hash of the commit (or the reference like origin/master) you want to "revert back to" on the master (/current) branch, e.g: git reset -hard a1b2c3d4 Git checkout newbranch # Go to the new branch that still has the desired commitsīut do make sure how many commits to go back. Git reset -hard HEAD~3 # Move master back by 3 commits (Make sure you know how many commits you need to go back) Git checkout master # checkout master, this is the place you want to go back Git branch newbranch # Create a new branch, saving the desired commits # Note: Any changes not committed will be lost. Unless there are other circumstances involved, this can be easily done by branching and rolling back. If you don't merge your changes first, they will be lost. If you want to move commits to an existing branch you need to merge your changes into the existing branch before executing git reset -hard HEAD~3 (see Moving to an existing branch above). WARNING: This method works because you are creating a new branch with the first command: git branch newbranch. ![]() Once complete, you can retrieve the stashed uncommitted edits with git stash pop Moving to a new branch ![]() ![]() You can store uncommitted edits to your stash before doing this, using git stash. Git reset -hard HEAD~3 # Go back 3 commits. If you want to move your commits to an existing branch, it will look like this: git checkout existingbranch
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |