Skip to content
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

New project creation only possible in empty directories #1485

Open
lfleck opened this issue May 13, 2024 · 3 comments · May be fixed by #1499
Open

New project creation only possible in empty directories #1485

lfleck opened this issue May 13, 2024 · 3 comments · May be fixed by #1499

Comments

@lfleck
Copy link

lfleck commented May 13, 2024

hatch new my-project currently requires an empty directory.
However, some workspaces may already contain files like a .devcontainer.json or the .git directory when starting the new project by cloning an empty remote repository.
While hatch --init can deal with this, it does not provide all features like creating the src-layout.
Is there a workaround to apply a project template to non-empty directories?
@ofek
Copy link
Sponsor Collaborator

ofek commented May 13, 2024

Does it work if you do hatch new project .?

@lfleck
Copy link
Author

lfleck commented May 13, 2024

Unfortunately not. This also raises the "Directory ... is not empty" error.

@ofek
Copy link
Sponsor Collaborator

ofek commented May 13, 2024

I'm totally open to someone adding a -f/--force flag!

@lfleck lfleck linked a pull request May 17, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add force flag for project creation in non-empty directories lfleck/hatch
2 participants
@ofek @lfleck