-
Notifications
You must be signed in to change notification settings - Fork 1
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
Configuration option to set overwrite #6
Comments
depending on if #7 is implemented it might be better to have something like |
Somewhat related to this, the plugin shouldn't do anything at all if the hash of the existing hook matches what it's trying to write (only do file modifications if necessary). Also, I think the default behavior should be to overwrite, but maybe warn or prompt or something if it's the first time it's happening? There are 2 use cases of "existing" hooks: A hook that this plugin didn't write
A hook the plugin did write, but now there's an update
Maybe we can differentiate between those 2 cases with a comment at the top of the file like |
something like this
should create an ERROR (but continue) if overwrite==true and file exists...
The text was updated successfully, but these errors were encountered: