Case-sensitivity in Bitbucket Cloud

Summary

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 Cloud 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 Cloud, it is treated as a new branch to the camel-case structure.

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

Example:

Branch names Feature1, feature1 can be created and are considered different.

Cause

Bitbucket Cloud completely relies on Git and Git is designed to be case-sensitive. Hence Bitbucket Cloud is case-sensitive. This means that a name in lowercase does not equal a name in camel-case.

Solution

Unfortunately, We do not have a solution yet as there isn't way in Git to enforce case insensitivity for branch names. One simple way to avoid issues is to always use all-lowercase branch and tag names.