You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you change the settings.yml file that points to the local Git repo workspace, the entire repo is removed and replaced. That means your hooks all get deleted. This happens when a 'rm' is issued on the repo folder.
The 'rm' is issued on any update of that file, whether deleting whitespace or changing a message for init or update.
So backup your live custom hooks that replace the built-in .sample files.
A good way to do this might be to edit your user settings.json and add to "syncSettings.additionalFiles" the local path to the folder where you maintain your hook scripts.
For this extension, perhaps a warning can be issued if there are any files in the repository/.git/hooks folder that do not have a .sample extension: (rm *.sample and then select the folder to see if there is still even a single file).
Or just add a warning to the README, which is the best place for warnings like this.
The text was updated successfully, but these errors were encountered:
If you change the settings.yml file that points to the local Git repo workspace, the entire repo is removed and replaced. That means your hooks all get deleted. This happens when a 'rm' is issued on the repo folder.
The 'rm' is issued on any update of that file, whether deleting whitespace or changing a message for init or update.
So backup your live custom hooks that replace the built-in .sample files.
A good way to do this might be to edit your user settings.json and add to "syncSettings.additionalFiles" the local path to the folder where you maintain your hook scripts.
For this extension, perhaps a warning can be issued if there are any files in the repository/.git/hooks folder that do not have a .sample extension: (rm *.sample and then select the folder to see if there is still even a single file).
Or just add a warning to the README, which is the best place for warnings like this.
The text was updated successfully, but these errors were encountered: