-1

enter image description hereenter image description here

I am using the Git source control in the VS Code. recently I found that if I create the branch like this, topic/CIE/LRAT-333, then I push that in to remote repo, finally in the VS code, choose source control on the left navigation, then click remote, I found that the branch folder became capital, TOPIC/CIE/LRAT-333. but when I check it in the azure repos, it is still "topic" lowercase.

I only this the capital topic here. TOPIC from the element

others are lowercase,  topic/CIE/LRAT-333 this is the screenshot from element

I found it's in the remote session. it's in remote session. here I attached another screenshot. enter image description here

so I don't know why it shows capital letter in the source control. it kind of bring us the confusion. could you please help me out?

Version: 1.76.2
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
Date: 2023-03-14T17:55:54.936Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.14393
Sandboxed: No

if it's lowercase, then it should be lowercase in the remote

Ferro Luca
  • 459
  • 11
user17900382
  • 1
  • 3
  • yes, I am using the gitlens., I already attached the screenshot – user17900382 Jul 12 '23 at 06:38
  • I can't see the picture in the description, but a link – user17900382 Jul 12 '23 at 06:41
  • does this happen for all your branches? If not, show all your branch names so we can see what the difference between them is. – starball Jul 12 '23 at 06:56
  • yes, for all branches. – user17900382 Jul 12 '23 at 07:09
  • Please always [edit] clarifications into your question post instead of hiding them in the comments! Comments are for _soliciting_ clarifications- not for providing them. – starball Jul 12 '23 at 08:37
  • I attached one screenshot in the problem description – user17900382 Jul 12 '23 at 08:54
  • it would be nice to have a screenshot that shows what element in the rendered page the element in the element inspector is associated with. – starball Jul 12 '23 at 08:58
  • I found that it's in remote session. – user17900382 Jul 12 '23 at 09:09
  • It's really hard to correlate what you're showing in the devtools screenshots to the actual VS Code workbench (window). I asked you to show a screenshot that also shows the workbench and highlights what the element corresponds to. – starball Jul 12 '23 at 09:13
  • I attached another one sceenshot, could you please help check – user17900382 Jul 12 '23 at 09:56
  • okay why does it now show "TOPIC" in remotes instead of "TOPIC/CIE/LRAT-333" like it showed in your earlier screenshot? – starball Jul 12 '23 at 09:58
  • I created another topic so it showed in seperated layers. topic/CIE/LRAT-333 and topic/CID/LRAT-334, like TOPIC ---CIE ----LRAT-333 ---CID ----LRAT-334 – user17900382 Jul 12 '23 at 10:37
  • if only one branch it showed "TOPIC/CIE/LRAT-333", but if more than one branch, it shows different lines, first line is TOPIC, second line the sub folders, and then in seperated sub folders, and third line shows the branch name – user17900382 Jul 12 '23 at 10:53

1 Answers1

0

Branches are by default organized as files and directories. Some file systems and operating systems are case-insensitive, such as Windows.

Check in your .git/refs/heads directory, if you find a TOPIC or topic directory (there can only be one).

To fix, you need to manually rename the directory (not really recommended), or rename all affected branches to something else, then after there are no more references to topic/TOPIC, rename them back.

Also make sure to update your remote accordingly (Linux generally is case-sensitive and topic/abc and TOPIC/abc are two completely distinct branches)

knittl
  • 246,190
  • 53
  • 318
  • 364
  • How should I manually rename the directory? – user17900382 Jul 12 '23 at 11:41
  • @user17900382 just like any other directory that you would rename. F2 in Windows Explorer, `ren` or `rename` in the command prompt. Copy, paste, then delete the old one. Take your pick – knittl Jul 12 '23 at 11:53
  • if this is your answer, why not dup vote to https://stackoverflow.com/q/15371866/11107541 ? – starball Jul 12 '23 at 16:36
  • 1
    @starball I wasn't aware of the dupe. Thanks for linking, I have closed the question now and linked the dupe – knittl Jul 12 '23 at 17:34