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.

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

Don't give up on linking just because some files already exist #7

Open
ro6 opened this issue Mar 8, 2022 · 1 comment
Open

Don't give up on linking just because some files already exist #7

ro6 opened this issue Mar 8, 2022 · 1 comment

Comments

@ro6
Copy link

ro6 commented Mar 8, 2022

I often end up running dploy into a directory where some subset of the files I'm linking to already exist. I'm glad I get warnings about that, and that it doesn't clobber the files, but I would prefer if it still went ahead and linked any files where there wasn't a conflict. If this behavior doesn't work for others' use cases as the default behavior, it could be hidden behind a flag.

@arecarn
Copy link
Owner

arecarn commented Mar 21, 2022

I could see how that might be useful. I'll see about adding that when I get some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants