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
I was using sml-sync on a project with multiple Git repositories. I deleted a folder containing one such repository and synced up. Now however I see this
And it persists no matter how many times I press [u]. I don't know what the best way to handle this is, I appreciate that deleting a Git repository is potentially dangerous, but perhaps there would be a better way of communicating to the user why the remote folder isn't getting deleted?
The text was updated successfully, but these errors were encountered:
@liamcoatman just pointed out that this is true for all files that are set as "ignored", e.g. __pycache__.
I think this should be the behaviour (in case there's a .git repo as in @tcbegley's case, or if there are notebooks or data files in a directory), but it should be communicated why the folders didn't get deleted (if that's possible).
One good idea by @tcbegley is to completely ignore directories that are empty (or perceived to be empty due to ignored files), similar to how git works
I was using
sml-sync
on a project with multiple Git repositories. I deleted a folder containing one such repository and synced up. Now however I see thisAnd it persists no matter how many times I press
[u]
. I don't know what the best way to handle this is, I appreciate that deleting a Git repository is potentially dangerous, but perhaps there would be a better way of communicating to the user why the remote folder isn't getting deleted?The text was updated successfully, but these errors were encountered: