Difference between git restore, reset & git checkout?

user_13126651 0
Viewed 1997

IN order to revert a item from staging area we use git reset filename or git reset .

however git also gives me a prompt (mentioned below) after I do git status.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)

This is also unstages file from staging area.

Also in order to revert changes there is known command

git checkout filename

However same can be achieved using git restore filename

What are the fundamental differences between them? and why git is pushing forward to use git restore

github git
1 Answers

Reverting the working tree version of a file to match the index version is one of many things git checkout can do (depending on what args you give it).

Reverting the index version of a file to match the version in the HEAD commit is one of many things git reset can do (depending on what args you give it). It is different from the above usage of checkout in that one changes the index and the other changes the worktree. (There are other checkout operations that also affect the index; and that's part of the issue that leads to the next point...)

git restore is a relatively new command that groups these functions together, while "un-grouping" them from the unrelated things those other commands do. The docs push toward using it because it's the newer, more clear way to perform the operations it covers. The operation is equivalent; it's just new porcelain to make git more usable.

I don't know what github has to do with using one command or the other. If there's some way in which you think they're pushing restore over the others, they'd be right anyway for the reason noted above - that it's the modern way to perform those operations.

user_70501300
Related