We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi! 馃槉
When you have a cookiecutter template that uses nested configuration files:
https://cookiecutter.readthedocs.io/en/stable/advanced/nested_config_files.html
.. cruft returns the following error when running cruft create <link>:
cruft create <link>
Was unable to locate a Cookiecutter template in `/var/folders/gk/w46bbths6x33p5rzz_771vch0000gn/T/tmp3qx91n5f` !
I can see that it is this function that fails since it searches in the root folder.
The text was updated successfully, but these errors were encountered:
Hello, I'm not facing exactly same issue but I want to use cruft with nested templates, so it's a bit related to yours.
My .cookiecutter.json looks like this
.cookiecutter.json
{ "templates" : { "project1": { "path": "./project1", "title": "Use Project 1 template" }, "project2": { "path": "./project2", "title": "Use Project 2 template" } } }
The following command
cruft create my-template
should prompt me
But it shows me,
![image](https://github.com/cruft/cruft/assets/71080989/d6b28059-6d2e-474c-87a6-b9db7500e603)
My template is in local but is doesn't change when I try to create my template from a remote repository
If somebody has a idea, it would be a pleasure to discuss about it :)
Sorry, something went wrong.
No branches or pull requests
Hi! 馃槉
When you have a cookiecutter template that uses nested configuration files:
https://cookiecutter.readthedocs.io/en/stable/advanced/nested_config_files.html
.. cruft returns the following error when running
cruft create <link>
:I can see that it is this function that fails since it searches in the root folder.
The text was updated successfully, but these errors were encountered: