Hello Guys!!
HEAD pointer movement
HEAD points to specific commit in the local repo-branch as new commits are made, the pointer changes
HEAD always points to the "tip" of the currently checked-out branch in the repo (not the working directory or staging index)
last state of repo (what was checkout initially HEAD points to parent of next commit(where writing next commit takes place)
HEAD Movement in Git branches |
Git Reset movements
This is most common need of every DevOps team development phase need. There are three options we have but of course two of them are mostly used.
Git reset movements at three tree levels |
- soft
- mixed
- hard
Using --soft reset
The soft reset command is to combine many commits into a single one.
git reset --soft HEAD (going back to HEAD) git reset --soft HEAD^ (going back to the commit before HEAD) git reset --soft HEAD~1 (equivalent to "^") git reset --soft HEAD~2 (going back to 2 commits before HEAD)
Using hard reset
move the HEAD pointer update the Staging Area (with the content that the HEAD is pointing to) update the Working Directory to match the Staging Areagit reset --hard HEAD (going back to HEAD) git reset --hard HEAD^ (going back to the commit before HEAD) git reset --hard HEAD~1 (equivalent to "^") git reset --hard HEAD~2 (going back two commits beforeBacking out changes to commit ids. So refer to the git show, git log commands in between to identify that change which you wish to reset to.
No comments:
Post a Comment