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 just gave isort a first try and used it in a clean svn working directory. I noticed that changes were applied to Python files below the .svn directory path. In my case, I was able to recover easily by trashing the working copy and check it out again; but for DCMS like git, mercurial etc. a destroyed working copy might be a much worse problem.
IMO, all "hidden" directories (including .git, .hg, .bzr as well) should be skipped by default.
There won't be anything we should directly change, right?
BTW, in this working copy I have a .gitignore file which could have been used to exclude .svn/.
However, this doesn't seem to work unless a .git/ directory is present as well; but this would be another issue.
The text was updated successfully, but these errors were encountered:
@tobiasherp Thanks for reporting this issue! .git and .hg were already skipped by default and thanks to your report I’ve added .bzr and .svn. The limitation on .gitignore is one of git itself (which isort uses for the functionality) and not isort itself.
I just gave isort a first try and used it in a clean svn working directory. I noticed that changes were applied to Python files below the
.svn
directory path. In my case, I was able to recover easily by trashing the working copy and check it out again; but for DCMS like git, mercurial etc. a destroyed working copy might be a much worse problem.IMO, all "hidden" directories (including
.git
,.hg
,.bzr
as well) should be skipped by default.There won't be anything we should directly change, right?
BTW, in this working copy I have a
.gitignore
file which could have been used to exclude.svn/
.However, this doesn't seem to work unless a
.git/
directory is present as well; but this would be another issue.The text was updated successfully, but these errors were encountered: