Apologies. I should obviously have mentioned which OSes the machines I tested on ran. One Windows 10 (fully updated) and one Windows Server 2016 (also updated). I've also seen it in a real repository on our build server which is Windows Server 2012 R2. After my first mail I updated git to latest and could still reproduce. On Aug 15, 2017 21:25, "Kevin Daudt" <me@xxxxxxxxx> wrote: On Tue, Aug 15, 2017 at 08:45:20PM +0200, Kim Birkelund wrote: > Hi > > I hope this is gonna sound as weird to you as it does to me. > > The link below is a zip of a small git repository that I can reproduce > the bug in on 2 machines. > > Repo: https://www.dropbox.com/s/fz4d0i5ko7s7ktr/test.zip?dl=0 > > It contains 2 folders: helpers and b, each of which is an empty npm > module. b\package.json refers to the helpers module. > > The following reproduces the bug: > > 1) in terminal cd to the b folder > 2) run npm install > 3) run git reset HEAD --hard > 4) run git clean -fdx > > At this point both files in the helpers folder has been deleted and > running git status confirms this. > > Tool version: > > git --version => git version 2.10.2.windows.1 > node -v => v6.11.2 > npm -v => 5.3.0 > > > I have no idea what is going. Very much hope you can explain :-) I cannot reproduce it on linux. git clean -fdx output: Removing node_modules/ Removing package-lock.json These are all untracked, and nothing in the helpers dir is being removed.
