Sigurd Spieckermann
Sigurd Spieckermann
Is your `copier.yml` file inside `cb-py-dev`? If so, it currently needs to be in the repo root. You can still keep your template content in the `cb-py-dev` directory by setting...
Odd, the test case is passing on CI macOS although the fix is commented out. So, the test case doesn't seem to reproduce the problem correctly. Does the test fail...
@kamontat Sorry for the delay. I was hoping we'd find a way to test this on the macOS runner. I find it a little suspicious why running the Copier CLI...
Tests on macOS and Windows are failing now – great! :tada: Thanks for figuring this out! :bow: You can enable the fix now, and when the tests pass, we can...
Now, several other tests are failing. 🤔
How about disabling `core.fsmonitor` in the local config of the cloned repository? IIUC, this feature isn't important for our use of Git.
Not sure if we're talking about the same approach – I might have expressed my suggestion badly. This is what I meant: We could disable `core.fsmonitor` in Copier's internal template...
Looks like this is working. :+1: Could you add an inline comment above that line with a link to this issue, so we'll remember why the `core.fsmonitor=false` setting is used...
Could you provide a reproducible example for us to better understand your specific workflow and the problems you're encountering? A minimal template (ideally created using shell commands) and a sequence...
Thanks for creating this PR to implement nested prompts, @dellekappa! :bow: I'll give feedback ASAP.