Currently, when you run the hatch command, the git repo will be downloaded inside that your current directory without creating a new sub-directory to contain all those files in. It's already expected from the user to create the sub-directory themselves and run the hatch command inside the sub-directory.
This seems like something Substance should handle itself considering that in most cases you don't want to clone the files directly where the substance command is called And that the default $ git clone behavior is to create a sub-directory name after the cloned repos name.
Currently, when you run the
hatchcommand, the git repo will be downloaded inside that your current directory without creating a new sub-directory to contain all those files in. It's already expected from the user to create the sub-directory themselves and run the hatch command inside the sub-directory.This seems like something Substance should handle itself considering that in most cases you don't want to clone the files directly where the substance command is called And that the default
$ git clonebehavior is to create a sub-directory name after the cloned repos name.