Hi,
and it does so if .gitignore has not been committed yet. This is with git version 2.6.3. To reproduce:
mkdir test cd test git init
echo "test" > test echo "something.txt" > .gitignore
git add test .gitignore git commit -a -m "init"
mkdir node_modules echo "something" > node_modules/file.txt echo "node_modules" >> .gitignore
git stash save -u
Now node_modules will be deleted even though it was ignored at the time of the "git stash save -u". Apparently .gitignore is reverted first, then the cleanup is done taking the new state of .gitignore into account where node_modules is now untracked and not ignored anymore, thus deleting it.
I think this should be considered a bug that can cause data loss, even if only in rare cases.
thanks, Michael
PS: I'm not subscribed.