Case-sensitivity in Bitbucket server
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Problem 1: Branches created on clients running on a mix of case sensitive and case insensitive operating systems may result in branch names with different letter case.
Example:
A branch is created on Bitbucket Server called feature/_. When this branch is checked out from a Git for Windows client it is recognized as origin/Feature_.
When this same branch is pushed from a git client on a case insensitive operating system (such as Windows or macOS) to Bitbucket Server, it is treated as a new branch to the camel-case structure.
Bitbucket Server now shows 2 branches: feature/_ and Feature/_ . Only feature/_ can be checked out.
(or)
Problem 2: Creation of branches with same name but different case is allowed in Bitbucket server.
Example:
Branch names Feature1, feature1 can be created and are considered different.
Cause
Bitbucket completely relies on Git and Git is designed to be case-sensitive. Hence Bitbucket server is case-sensitive. This means that a name in lowercase does not equal a name in camel-case.
Resolution
Unfortunately, We do not have a solution yet as there isn't way in Git to enforce case insensitivity for branch names. We have a feature request in place in Bitbucket.
Was this helpful?