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


Issue #3348 open

Allow uppercase characters in repo slugs (BB-3175)

Rob Allen
created an issue

If you create a repository called CStest then the git repo name git@git.bitbucket.org:akrabat/cstest.git

This is surprising and confused some scripts I have that tried to push to git@git.bitbucket.org:akrabat/CStest.git!

Please honour the case of the repository name.

Comments (20)

  1. Mehmet Catalbas

    Hi Rob,

    The repo URLs contain the slug (generated using repo name obviously), not the name itself, and it'll always be lowercase, it's always been. Slugs are generally used like this in URLs all over the web.

  2. David Chambers

    I'd like to revisit this issue. While in general I prefer URLs not to contain uppercase characters, the fact that repo slugs are used as directory names makes this a special case. It's not uncommon for a directory's name to have special significance, as in this example:

    cd /Applications/Coda.app/Contents/Resources/Modes
    mv Javascript.mode Javascript.mode.orig
    hg clone https://bitbucket.org/davidchambers/javascript.mode Javascript.mode

    Ideally the final command would read:

    hg clone https://bitbucket.org/davidchambers/Javascript.mode

    I'll accept a "J" in my URL in exchange for simpler setup instructions. The point is that this trade-off should be considered on a case-by-case basis by users, not globally by us.

  3. Anonymous

    would love to see this changed, as I have a case sensitive folder and when I clone from git, I need to remember to manually change some letters to uppercase as copy/pasting the git clone would cause issues!

  4. Francois Gervais

    What's the state of the issue?

    In about 2-3 month we want our source code to be hosted online. We have a lot of repositories with capital letters in the folder name. Any chance this will be fixed in this time frame?

  5. Micky Hulse

    I'm trying to organize projects that are named like XN201.A1. This is how others in my company expect to see them on their filesystem. As much as I don't like all caps in my urls, it's definitely not desirable to lowercase these names, in this situation.

    With that said, I suppose I can clone into a folder that is all caps … Just means I have to do a tiny bit more hand holding.

    Anyway, +1 from me.

  6. Lea Hayes

    Unless this issue is resolved it might become necessary to use GitHub for my current project.

    Would it not be easy to simply ignore casing when a URL is requested such that all of the following commands would yield the exact same result (the tooling will assume the character casing requested in the command):

    hg clone https://bitbucket.org/davidchambers/javascript.mode
    hg clone https://bitbucket.org/davidchambers/Javascript.mode
    hg clone https://bitbucket.org/davidchambers/JaVaScRiPt.mOdE
    hg clone https://bitbucket.org/davidchambers/JAVASCRIPT.MODE

    As far as Bitbucket is concerned, why can't it just convert the slug to lower case instead of yielding a 404 page?

    Aside: In my case I'm using git.

  7. Jeff Shanab

    I definitely vote for honoring mixed case in this part. It causes more problems than it fixes. This is a decision for the author and not source control which should not change the contents stored on it's own.

  8. Douglas Gadêlha

    Quick and Simple Tip: Move to GitLab.

    Atlassian seems to show no interest in helping users, neither accepts their feedbacks.

    It's UGLY to have full lowercase name as repo slug. And yes, we do care about that, Atlassian.

    Ah, don't forget: This issue is 5 years old.

  9. Log in to comment