GitHub, GitLab, and Atlassian BitBucket are all sites that offer git repository hosting. But if you create a repo named “Test” with BitBucket, then you copy/paste the slug URL  and feed it to “git clone” as usual,  the URL is forced to all lower case  “test” and you end up with a clone of your repo in directory(folder) “test”. This stinks, for example, with common library directory naming conventions.

After thrashing around in the team settings, thinking I’d just missed the way to override the default URL, it occurred to me this might be a feature, not a bug. Sure enough:

https://jira.atlassian.com/browse/BSERV-3148

(“Stash” is simply Atlassian’s downloadable repo hosting system, effectively giving a customer a “Bitbucket” system within their enterprise)

This is just a classic bug report pattern. Who knows what caused the Bitbucket architect to decide not to honor the name spelling when creating the slug (the text box holding the URL you copy from to do a clone). But, the fact that one can simply modify the URL and end up with a target directory with any pattern of upper/lowercase makes it clear that they COULD offer an “honor name capitalization” radio button to override their sacred cow default, but they choose not to, with the lamest of lame excuses:

“Given that it is possible to modify the clone URL to include a camel-cased repository name (which creates a camel-cased repository directory when cloning), this is unlikely to be a priority in the near future.”

But this latest submission was started in 2013 and “resolved” in 2015, two years ago. Maybe it’s time to submit it again.