-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Cloning error on case-insensitive filesystems #5891
Labels
Comments
aryanrawlani28
changed the title
Fix cloning error on case-insensitive filesystems
Cloning error on case-insensitive filesystems
Sep 30, 2020
Nice work on identifying and fixing the issue 👍 It is important to make things work across all different environments. |
Hey @aryanrawlani28 @AdiChat I was wondering if this issue is open? If it is, I would like to Contribute to it and could you please guide me on this? |
beef-erikson
added a commit
to beef-erikson/cosmos
that referenced
this issue
Oct 4, 2022
…other conflicting file.
Just now noticed this was a closed issue. Followed the link from Octoberfest. Disregard my pull request; I shall look into current bugs! Thanks! |
AdiChat
added a commit
that referenced
this issue
Oct 6, 2022
Fix for issue #5891, removed file causing issue and renamed other con…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a(n):
Details:
Hello.
I'm currently on a Windows platform, which is a case-insensitive filesystem. Upon cloning the repository, it gives me the below log:
This is because these files are the same name, just capitalization is different. Thus,
scripts/metadata/code/design_pattern/src/oop_patterns/data.json
needs to be deleted - because anotherOOP_patterns
folder exists.code/dynamic_programming/src/longest_common_substring/longest_common_substring.cpp
needs to be renamed, because one solution already exists.PR #5890 tries to fix this.
The text was updated successfully, but these errors were encountered: