Case-sensitivity in Bitbucket server

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および Crucible は除く

問題

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. 

例:

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.

例:  

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


原因

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.

ソリューション

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.

BSERV-8361 - Getting issue details... STATUS


最終更新日 2021 年 7 月 29 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.