Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about CollectivesStack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git statusgit status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
Update: I have this in my config file
$ git config alias.unstage reset HEAD which I usually use to unstage stuff.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
Update: I have this in my config file
$ git config alias.unstage reset HEAD which I usually use to unstage stuff.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
Update: I have this in my config file
$ git config alias.unstage reset HEAD which I usually use to unstage stuff.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
Update: I have this in my config file
$ git config alias.unstage reset HEAD which I usually use to unstage stuff.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
Update: I have this in my config file
$ git config alias.unstage reset HEAD which I usually use to unstage stuff.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.
The output tells you what you need to do. git reset HEAD cc.properties etc.
The output tells you what you need to do. git reset HEAD cc.properties etc.
This will unstage the rm operation. After that, running a git status again will tell you that you need to do a git checkout -- cc.properties to get the file back.