Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The documentation states that leveraging the --soft option “…Does not touch the index file nor the working tree at all, but requires them to be in a good order. This leaves all your changed files “Changes to be committed”, as git status would put it”.
It also explains that the target <commit> defaults to HEAD, when not given.
Considering these, does the following command modify anything at all?
$ git reset --soft
No, it is a no-op.
After thinking about this for a bit: technically it will complain if you are in the middle of a merge with unresolved conflicts however all that this means is that instead of doing nothing, it complains and does nothing.