Conclusion#

• Use commands to find case-sensitive conflicts → keep one → delete redundant branches, and you can resolve Git fetch/pull failures.

Applicable Scenarios#

• Windows / Mac developers encountering Git pull failures
• Teams using a mix of Linux + Windows
• Lack of unified branch naming conventions
• CI/CD suddenly unable to find branches

Step-by-Step Process#

1
git ls-remote --heads origin |
2
ForEach-Object { ($_ -split "`t")[1] } |
3
Group-Object { $_.ToLower() } |
4
Where-Object { $_.Count -gt 1 } |
5
Select-Object -ExpandProperty Group

1
git push origin --delete Feature/Login

1
git fetch --prune

Additional Notes#

• Windows / Mac default to case-insensitive file systems, while Linux is case-sensitive → source of conflict
• It is not recommended to use the reftable solution, as tool support is still unstable.
• If CI/CD is tied to the wrong branch, confirm the pipeline before deleting.

Command / Example Summary#

1
# 找出大小寫衝突
2
git ls-remote --heads origin |
3
ForEach-Object { ($_ -split "`t")[1] } |
4
Group-Object { $_.ToLower() } |
5
Where-Object { $_.Count -gt 1 } |
6
Select-Object -ExpandProperty Group

1
# 自訂 function
2
function Find-GitCaseConflict {
3
    git ls-remote --heads origin |
4
    ForEach-Object { ($_ -split "`t")[1] } |
5
    Group-Object { $_.ToLower() } |
6
    Where-Object { $_.Count -gt 1 } |
7
    Select-Object -ExpandProperty Group
8
}

1
# 刪除遠端分支
2
git push origin --delete Feature/Login
3

4
# 清理本地
5
git fetch --prune

Wrap-up#

• Inconsistent Git branch casing is a ticking time bomb.
• It is recommended to standardize naming (all lowercase) from the beginning to avoid many pitfalls later.