Case-sensitivity in branch name causes issue

お困りですか?

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

コミュニティに質問

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

問題

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.

原因

Both Git and Bitbucket Server are designed to be case sensitive. This means that a name in lowercase does not equal a name in camel-case.

ソリューション

Git can be configured to be case insensitive by adding the following to the [core] section of the .git/config file:


ignorecase = true


Also, ensure that the bitbucket.properties file does not contain this setting:

plugin.bitbucket-branch-permissions.case.insensitive=false



最終更新日: 2019 年 12 月 20 日

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

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