-
I'm new to copier. I'm trying to develop test units so that I can test changes I'm implementing. Project generation (aka. copy) works well. My problem relates to testing changes from a dirty git repo, with uncommitted changes, and potentially new files. In my first test, I'm trying to run an update using the same state of the (dirty) git repo that generated a copy. Here is a sketch of I'm trying to do:
a) A file called _min_copier_version: '9'
_exclude:
- .git
- copier.yml
project_name:
type: str
default: new-foo
help: A short (slug-style) name for your project b) a file called _min_copier_version: '9'
_exclude:
- .git
- copier.yml
project_name:
type: str
default: new-foo
help: Help for project-name
Of course, the commit How can I make the update from a dirty repo work as described above? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I must be going crazy... I just realised that what I'm implying here is not a valid use-case. It does not make sense to a) update a project w/o actual changes and b) in case of uncommitted changes, there is no way to track those without a commit! I'm sorry for the noise. |
Beta Was this translation helpful? Give feedback.
I must be going crazy... I just realised that what I'm implying here is not a valid use-case. It does not make sense to a) update a project w/o actual changes and b) in case of uncommitted changes, there is no way to track those without a commit! I'm sorry for the noise.