Suggestion: ssc init should warn when run on a non-empty directory

[WesSouza]

I ran ssc init without realizing it would put files in the current directory (and ask for a project name like many other init commands do).

Running it in a folder with contents should ask the user before creating files.

[chicoxyzzy]

@heapwolf I remember you was opposed to make ssc accept user input, but I think this case makes sense.

[WesSouza]

@chicoxyzzy it could also fail and require a flag like --force.

[heapwolf]

Yeah I prefer it to fail with Directory not empty. Refusing to init. To override use --force flag. , +1 on --force, PR welcome!

[iamfotx]

Hi, @chicoxyzzy & @heapwolf I'd love to take this one, can do it over the weekend if that's fine?

[chicoxyzzy]

This was fixed in #239 in a bit different way. ssc init warns instead of trying to replace files