Don't checkout anything by default on local templates

I’m currently translating a cookiecutter template to a copier one, and each time I change something, I have to commit the change for copier to pick it up. At first it was confusing (“why did files that I removed were copied??”), and now it’s annoying (a “wip” commit for every change, and then I’ll have to squash them or something).

I think it’s because copier tries to checkout the latest tag? I’d like it not to do anything if I don’t specify the -r, --vcs-ref option.

[yajo]

As a user I want to be able to test templates quickly/iteratively using existing cli tool (not via pytest fixture)

Yes, well that makes sense indeed.

However, I cannot predict what you want to test. Is it a copy, a recopy or an update? Besides, when copying a non-git template, the results and features are different, so you could get to unexpected results when comparing your dev with production environments.

However I guess that we can make this assumption: if the template is a local directory and it is dirty, you’re developing the template, so you’re going to want to test those dirty changes, so Copier could take the freedom to do the wip commit dance automatically and print a warning so you are aware of that.

[pawamoy]

Oh yes, thank you! I happen to have written my tests in a simple shell script though 😅

But I’ll use your fixture if I convert them to a pytest suite.