You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem
It seems like (please correct me if I'm wrong) that the default directory structure that copier expects when generating or reading a subproject is as follows:
repo/
.git
.copier-answers.yml
project/
src/
I have been having problems with update with a directory structure like this
repo/
.git
.copier-answers.yml
src/ # please note the src is at the root of the repo right next to .coper-answers.yml
When I run update, copier does the following:
repo/
repo/ # note the project is recreated inside the current project instead of overwriting
.copier-answers.yml
src/
.git
.copier-answers.yml
src/
Note that instead of updating the project, it creates the project again as a nested folder inside the current project.
I ended up doing the same however, admittedly, it would be lovely if copier could support the original use case. It will make for an ever more streamlined and friendly experience in my humble opinion. @yajo pretty please? Alternatively could you please explain why such use case is not supported?
@debo the original issue is not clear to me. It shows commands that do not exist (copier template). I'd suggest you open a new discussion with your detailed use case.
Describe the problem
It seems like (please correct me if I'm wrong) that the default directory structure that copier expects when generating or reading a subproject is as follows:
I have been having problems with update with a directory structure like this
When I run update, copier does the following:
Note that instead of updating the project, it creates the project again as a nested folder inside the current project.
Template
A template structure like so:
To Reproduce
copier template .
with the mentioned template structurecopier update
Logs
Expected behavior
Copier should update the existing project instead of creating a nested folder.
Screenshots/screencasts/logs
Environment
Additional context
The text was updated successfully, but these errors were encountered: