Repository Name is case insensitive

Issue #4374 open
Gianluca Padovani
created an issue

I imported a git repository called "MyRepo" but in bitbucket is named "myrepo" so when I deploy my application on linux machine the directory is called "myrepo" not "MyRepo".

Comments (24)

  1. Gianluca Padovani reporter

    (Reply via

    I don't try with hg repo but I suppose you are correct. The problem is that in my deployment script, I use capistrano, my application is called in case sensitive name (MyRepo), so when the repo is cloned the command doesn't work.

    2012/7/25 Denis Ryleev <>:

  2. Gianluca Padovani reporter

    (Reply via

    Probably in this way will work If you have a new deployment. I have already a deployment active in a directory called "MyRepo" so I should rename it in myrepo, change some path in Apache configuration, etc ...

    Probably I'll do it because I want use bitbucket instead of my private repo. I hope that Bitbucket will be case sensitive in the future ... :-)

    thank you Gianluca

    2012/7/25 Denis R <>:

  3. Yif Dai

    But the question is "Is this a good design?". You should give the user the freedom to name her repository as she likes, rather than default the name she has chosen to whatever you prefer. This is not only a concern of inconvenience, it is just inconsistent or controversial to file name conventions promoted by almost all modern OSes.

  4. Jerry Tromp

    Especially annoying when you just moved 60 projects from GitHub to BitBucket, where as on GitHub case sensitive reposlugs are actually allowed. Shame this is not considered something to be fixed.

  5. ozgurm

    xCode ise case sensitive so when i fix my file name and i couldnt commit it, i figured out like this, change file name and commit, after that fix the name and commit with push,

    but still meanless why dont you fix this.


    Thanks Ana! Just migrated all my repos to Bitbucket only to find my developers complaining that things don't work out of the box and they have to rename the repo after it is cloned. A very minor but, as others have said, annoying thing. And something that I have to keep answering questions about (developers, as it turns out, don't always read documentation).

  7. David Backstein

    Please add case sensitive repos. I totally agree with Hong: "it is just inconsistent or controversial to file name conventions promoted by almost all modern OSes"

    What is the point of forcing the user to have lowercase repo names? Sure, I can check out the repo using any uppercase and lowercase version of my repo name. Perfect to maximize the confusion among your employees when you switch to a serious GIT hosting company . . . nothing will work if any upper/lowercase version is allowed and each user can choose by random how he writes it.

  8. AnumSheraz

    i was facing same issue, but seems like changing the url did the trick. My original repo name was FlaskApp and the url I got from bitBucket was git clone And I pasted it in my terminal as git clone , which worked Perfect !

  9. Log in to comment