Describe the bug
If you set the output folder to be in the same folder as the template folder, boilerplate does unnecessary multiple passes of the output folder, presumably due to the fact that the output folder is created first.
Expected behavior
Boilerplate should only render the output folder once.
Additional context
Alternatively, we should consider preventing the user from setting an output folder within the template folder, since that can lead to all sorts of unexpected issues, such as breaking idempotency (if you run twice, the output folder will be processed as a template by boilerplate.
Describe the bug If you set the output folder to be in the same folder as the template folder, boilerplate does unnecessary multiple passes of the output folder, presumably due to the fact that the output folder is created first.
Expected behavior Boilerplate should only render the output folder once.
Additional context Alternatively, we should consider preventing the user from setting an output folder within the template folder, since that can lead to all sorts of unexpected issues, such as breaking idempotency (if you run twice, the output folder will be processed as a template by
boilerplate
.