threads / discuss / 19436

git reset --hard and uncommitted files in index

Subject: git reset --hard and uncommitted files in index

## tl;dr

3 messages between May 22, 2009 and May 22, 2009.

replies: 2people: 3as markdown or json

Thomas Guyot-Sionnest· May 22, 2009, 02:32 UTC · lore

Hi,

Today I was working on a script that modify many files on a repository, therefore during testing phase I needed to reset --hard to get back to the last commit. This operation does not affect untracked files.

Since i was going to commit the script, at some point I decided to add it to the index so I could track/revert changes to it. On the next reset Git deleted the script.

Fortunately "git add" creates an object that I could easily recover (thanks to wereHamster on #git for pointing that out), however I was wondering if it's really the desired behavior to *delete* a file that have been added to the index but isn't on the previous commit? Shouldn't git just unstage it?

-- Thomas

Johannes Sixt· May 22, 2009, 06:43 UTC · re: Thomas Guyot-Sionnest · lore

Re: git reset --hard and uncommitted files in index

Thomas Guyot-Sionnest schrieb:

Show 13 quoted lines

> Today I was working on a script that modify many files on a repository,
> therefore during testing phase I needed to reset --hard to get back to
> the last commit. This operation does not affect untracked files.
> 
> Since i was going to commit the script, at some point I decided to add
> it to the index so I could track/revert changes to it. On the next reset
> Git deleted the script.
> 
> Fortunately "git add" creates an object that I could easily recover
> (thanks to wereHamster on #git for pointing that out), however I was
> wondering if it's really the desired behavior to *delete* a file that
> have been added to the index but isn't on the previous commit? Shouldn't
> git just unstage it?

No, the behavior is by design. Its purpose is to return the working directory to a clean slate. For example, after a conflicted merge the merged branch may have brought new files, but you wouldn't want to keep them around after the cleanup.

'git reset --hard' is "do what I say", not "do what I mean". ;-)

-- Hannes

Sverre Rabbelier· May 22, 2009, 10:50 UTC · re: Thomas Guyot-Sionnest · lore

Re: git reset --hard and uncommitted files in index

Heya,

On Fri, May 22, 2009 at 04:32, Thomas Guyot-Sionnest <dermoth@aei.ca> wrote:

> Shouldn't git just unstage it?

You can do that too, 'git reset && git reset --hard' will not touch untracked files. The first will unstage all your changes, the second will blow away all changes to tracked files.

-- 
Cheers,

Sverre Rabbelier