dest directory does not exists when executing actions about degit HOT 4 CLOSED

Sorry for the delay on this and for the problem in the first place! The short answer is I wasn't accounting for running a remove action without a clone action first. So what was happening was:

1. You clone down your repo
2. You files are stashed because degit assumed the files in your repo were the final ones you wanted
3. It runs your remove command but things are stashed so nothing happens
4. Your files get unstashed and you get your original files

The use case I was designing for is

1. Same as above
2. Same as above
3. I figured you would have a clone command here to bring in some new files
4. You have a remove command here to get rid of files from step three
5. Your files get unstashed and you get your original files, overwriting any files currently in your directory from step 3 since degit assumes files that you began with are the ones you want to end with

This isn't how it should work though and you should be able to remove files locally first, as I had said was possible.

This PR fixes the issue with more sensible stashing / unstashing and better explains the desired logic: #65 Let me know what you think!

from degit.

I assumed that the use case you describe is the one the action is intended for, am I wrong?

from degit.

That's absolutely correct. The action is intended for removing list of files.

from degit.

@mhkeller ?

from degit.