On Fri, Mar 01, 2019 at 07:56:00AM +0100, Johannes Sixt wrote: > Am 28.02.19 um 22:43 schrieb Manuel Guilamo: > > I accidentally executed git reset —hard in a project that doesn’t > > have any commits yet. git erased everything, everything I’ve worked > > the past week, I believe this is not a desired behavior, considering > > I’m not able to undo that action, because git doesn’t have any > > history whatsoever. > > I tested this, and it does not happen for me as long as I do not `git > add` anything. > > So, I assume you did `git add` your content and then you did a `git > reset --hard`. In that case, I'm afraid Git behaved as designed and > "doesn't have any commits" is a red herring. Wouldn't that mean all of the file data is available in the object database? Unfortunately without an index, there's nothing to mark which file was which. But `git fsck --lost-found` should copy out all of the file content into .git/lost-found. -Peff
