Allow uppercase characters in repo slugs (BB-3175)

Issue #3348 open
Rob Allen created an issue

If you create a repository called CStest then the git repo name

This is surprising and confused some scripts I have that tried to push to!

Please honour the case of the repository name.

Comments (30)

  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/
    mv Javascript.mode Javascript.mode.orig
    hg clone Javascript.mode

    Ideally the final command would read:

    hg clone

    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. Former user Account Deleted

    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. Nathan McGinn

    SAP recommends using uppercase project names, and way we can add support for this? Seems like a really simple change.

  5. 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?

  6. Darryl Young

    I'm also here for the issue that repository names are forced to lowercase. This issue has been around on here for a very long time now (in various forms).

  7. 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.

  8. 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
    hg clone
    hg clone
    hg clone

    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.

  9. 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.

  10. Timofey Mukha

    I would like to express my support for mixed case in repo names, it's quite common to have a capital letter inthe project name.

  11. Former user Account Deleted

    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.

  12. Mike Laster

    Can you please fix this? The case used in the repo slug ends up being the default name of the cloned repository, and it ends up being wrong to checkout "MyProject" to a directory called "my project".

  13. Mohammed El-Beltagy

    Just discovered this today. Truly annoying. Can't believe it has been that way for SIX years!

  14. Michael Abdallah-Minciotti

    I, too, need to have multiple repositories with mixed case as all of our build files are built as such. When will this issue finally be resolved?

  15. hillierlab

    Honestly, I am surprised by the unwillingness to make this relatively trivial fix for us. I cannot refactor 100k lines of code and tell collaborators that atlassian has its own mindset. I made an attempt to migrate from github but I am now convinced github is the way to go.

  16. Ed Barry

    I'm moving to GitLab for this very reason. I am sick of my includes being linked to paths with names that get changed to lower case.

  17. Log in to comment