1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #4873 wontfix

Use of CamelCase in repo name on Git repo URL

Anonymous created an issue

I would like to see that Bitbucket doesn't destroy the case of my Git repo name. If I decide to name my repository eg. 'MyCoolCustomControl' on creating it and Bitbucket give me a URL like:


then it is not the thing I was expecting to get. The reason is quite simple: If I develop reusable components (in my example this is MyCoolCustomControl control) I'm aware of using camel case, because it's related to the (main) class name of this component. So, if someone clone it from Bitbucket the root directory of this local repo will have the wrong case.

Comments (5)

  1. Dylan Etkin

    Hi Frank,

    I am sorry this is not what you are looking for.

    We lowercase the reponame so that we don't get polluted namespaces. It is the much more likely case that someone does not want to care about case and that they will feel like the site has misbehaved if they ask for the wrong case and do not get the repo they are looking for.

    I hope you understand, cheers,


  2. David Hollingshead

    I discovered that if I save a text file with the repos properly cased in the URL, I can still use them to clone (I use Git Extensions on Windows which automatically creates the folder cased as it is in the URL); so there's no reason to not match the case in the URL to the repos, lowercasing them simply creates an unnecessary inconvenience for the user.

    We develop on Windows and deploy on IBM (AIX), and keeping the case in the URL would solve all problems. Changing the case allows folders with the same name to be deployed on AIX and clash on Windows. There's no reason from your user's end to change the case, and creates multiple problems.

    I was trying to find out if there was a problem on your end from keeping the case the same in the URL, and it sounds like you've had to jump through more hoops to deal with it being lowercased in the URL, which is also causing us to jump through more hoops.

  3. Log in to comment