Skip to content

Find directory_name in copier #403

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.

Sign up for GitHub

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

Jump to bottom
Closed
lyashevska opened this issue Jul 30, 2024 · 2 comments
Closed

Find directory_name in copier #403

lyashevska opened this issue Jul 30, 2024 · 2 comments
Labels
copier

Comments

@lyashevska
Copy link
Member

Copier takes {{directory_name}} (=destination) as an input via copier copy source destination instead of asking user a question.

Following files refer to it:

./copier.yml
./tests/test_values.py
./template/README.md.jinja
./template/project_setup.md.jinja
./template/next_steps.md.jinja
./template/.github/next_steps/03_readthedocs.md.jinja
./template/.github/next_steps/01_sonarcloud_integration.md.jinja
./template/sonar-project.properties.jinja
./CHANGELOG.md
./setup.cfg
./README.md

Can we get away without directory name?
@egpbos
Copy link
Member

egpbos commented Jul 31, 2024

I guess it sort of makes sense to not use the top-level directory name inside the repo, since anyway that can be changed by the user. You could replace it by a generic placeholder, or just assume (or suggest) that you are inside the repository root dir for all commands given. That could make some readme texts a bit esoteric though...

@lyashevska lyashevska mentioned this issue Aug 1, 2024
Merged
3 tasks
@lyashevska
Copy link
Member Author

Fixed in ##411

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
copier
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@egpbos @lyashevska