Where git checkout solely operates on the HEAD ref pointer, git reset will move the HEAD ref pointer and the current branch ref pointer. How it worksĪt a surface level, git reset is similar in behavior to git checkout. Now that we have followed this changeset through the three trees we can begin to utilize git reset. Executing git log will display the Commit History. Invoking git status at this point shows that there are no pending changes to any of the trees. The changeset has been added to the Commit History. Here we have created a new commit with a message of "update content of resetlifecyclefile". $ git commit -am"update content of reset_lifecycle_file" update content of reset_lifecycle_file 1 file changed, 1 insertion(+) $ git status On branch main nothing to commit, working tree clean This snapshot also includes the state of the Staging Index at the time of commit. The git commit command adds changes to a permanent snapshot that lives in the Commit History. Let us examine the Staging Index content at this point.
The git status command output displays changes between the Commit History and the Staging Index. It is important to note that git status is not a true representation of the Staging Index. Invoking git status now shows reset_lifecycle_file in green under "Changes to be committed".
Here we have invoked git add reset_lifecycle_file which adds the file to the Staging Index. The git ls-files command is essentially a debug utility for inspecting the state of the Staging Index tree. To accurately view the state of the Staging Index we must utilize a lesser known Git command git ls-files. Git generally tries to hide the implementation details of the Staging Index from the user. This tree is a complex internal caching mechanism. This tree is tracking Working Directory changes, that have been promoted with git add, to be stored in the next commit. They will be displayed in the red with a 'modified' prefix. Git status can be used to show changes to the Working Directory. These changes are currently a part of the first tree, "The Working Directory". Invoking git status shows that Git is aware of the changes to the file. In our demo repository, we modify and add some content to the reset_lifecycle_file. " to discard changes in working directory) The gco abbreviation for git checkout is very useful, allowing me to type: gco Īlso, I often mistype git as get or got so I created aliases for them too.$ echo 'hello git reset' > reset_lifecycle_file If your shell supports aliases, or shortcuts, you can add aliases on this level, too. We will talk about the git branch command very soon, and the git cat-file command is useful for exploring git. We’ve added a few aliases for commands we haven’t yet discussed. gitconfig file before continuing if you wish to repeat my actions. Make sure you have a hist alias setup in your. The only exception is that I will use the hist alias defined above, when I need to see the git log.
GIT STATUS FULL
gitconfig fileįor the most part, I will continue to type out the full command in these instructions. Best of all, the git hist command will help you avoid the really long log command. The most important thing to learn from this lesson is that you can type git st wherever you had to type git status. In the previous lesson we covered the log command and will get to know the checkout command very soon. We’ve already talked about commit and status commands. Hist = log -pretty=format:\"%h %ad | %s%d \" -graph -date=short Git status, git add, git commit, and git checkout are common commands so it is a good idea to have abbreviations for them.Īdd the following to the. Git config -global alias.dump 'cat-file -p' Git config -global alias.type 'cat-file -t' Git config -global alias.hist "log -pretty=format:'%h %ad | %s%d ' -graph -date=short"
GIT STATUS HOW TO
0 kommentar(er)
