-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add force option #15
Comments
Here's an idea: If the symlink target is under version control and it is checked in, I think it is more interesting to have an option to force-move the current inhabitant of the symlink location into the git repository and then create the symlink as normal. This should emit a warning and at the end a helpful suggestion for what to do about it. "review the differences; restore the file to the original, or edit and commit the changes". |
That would be a useful feature for some (maybe most?) users, but I am personally not planning to modify this tool to use or assume the existence of any particular version control system. It's a tool for making symlinks. |
I have made a fork here, currently for my own benefit only. Let me know if you would like a PR. |
Interesting! I like that you were able to break these improvements down into features that do/do not depend on version control. I'll take a closer look asap. |
This should force the creation of symlinks on install.
It should delete whatever file is in the expected location on uninstall.
It should probably not delete non-empty directories on uninstall.
The text was updated successfully, but these errors were encountered: