-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Template files/directories with customisable names #14273
New issue
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This would indeed be a very useful feature, cookiecutter can also do that, and is probably the reference solution for Python project templates. |
An alternate route could be a gitea actions trigger for when a template is uses. That would allow for completely customizable behavior when using templates |
I think #25294 added this to Gitea 1.21.0, so it seems this can be closed now. |
Automatically locked because of our CONTRIBUTING guidelines |
Description
Right now, template variables are only expanded within file contents. It would be nice to be able to also expand them inside file names. One potential use case for this is to create a
$REPO_NAME
directory for storing a template Python module with the same name as the repository.One potential issue with directly allowing variables in file names is that this could potentially induce non-determinant behaviour depending on the order in which the files are renamed. We could simply error if renaming a file results in overwriting another file, however.
The text was updated successfully, but these errors were encountered: