-
-
Notifications
You must be signed in to change notification settings - Fork 709
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
check-case-conflict doesn't notice directory name conflicts #70
Comments
Whoops, I think this is my fault. This is a use case I didn't think of. To fix this I'm thinking that when we generate the set of relevant files to check for conflicts, we should also add to the set all of the parent directories/paths of those relevant files. This has the potential to get messy/inefficient though. |
@guykisel Has it been fixed? |
@dizel3d it has not, that is why this issue is still open |
slsyy
added a commit
to slsyy/pre-commit-hooks-1
that referenced
this issue
Mar 19, 2021
slsyy
added a commit
to slsyy/pre-commit-hooks-1
that referenced
this issue
Mar 19, 2021
slsyy
added a commit
to slsyy/pre-commit-hooks-1
that referenced
this issue
Mar 19, 2021
asottile
pushed a commit
to slsyy/pre-commit-hooks-1
that referenced
this issue
Apr 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A conflict such as
Test/foo
andtest/foo
is caught though.The text was updated successfully, but these errors were encountered: