{"thread":{"id":"66128","subject":"Branch renaming shortage","startedAt":"2026-08-06T10:39:36Z","lastAt":"2026-08-06T10:39:36Z","messageCount":1,"participants":["Piotr Slowinski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"549824","messageId":"LV9PR19MB913344C2C359F1A86C329B3DF7D22@LV9PR19MB9133.namprd19.prod.outlook.com","threadId":"66128","inReplyTo":null,"subject":"Branch renaming shortage","fromName":"Piotr Slowinski","fromEmail":"piotr.slowinski@bentley.com","sentAt":"2026-08-06T10:39:31Z","receivedAt":"2026-08-06T10:39:36Z","isPatch":false,"body":"Hi,\n\nI found an issue with local repo update.\nHave one remote Repo and 2 local copies of it: Local1 and Local2.\nOn Local1 create branch \"mybranch\", so some modifications and push to remote.\nFetch/pull on Local2, relevant file \".git\\logs\\refs\\remotes\\origin\\mybranch\" file is created.\nNow on any local, but let's stay with Local1 change character of that branch to root of subbranches.\nEg. Rename \"mybranch\" to \" mybranch/WIP\".\nProbably this will likely suffice, but I also added another node and sub-nodes, like\nmybranch/archive/branch1\nmybranch/archive/branch2.\nCommit and push - all fine.\nNow try to fetch/pull on Local2 - GIT complains about \".git\\logs\\refs\\remotes\\origin\\mybranch\" and that is because locally it is a file whilst GIT assumes it to be no folder and want to write into.\n\ngit version 2.51.0.windows.2\n\nManual delete on Local2 \".git\\logs\\refs\\remotes\\origin\\mybranch\" file and git fetch/pull creates relevant structure.\n\nTIA,\nP\n\n________________________________\n\n\n\nThis email, including any attachments, may contain confidential and/or proprietary information intended only for the use of the recipient. If you are not the intended recipient, any distribution, copying, or use of this email or its attachments is prohibited. If you received this email in error, please reply to the sender immediately and delete this message and any copies.\n\nBentley Systems has taken all reasonable steps to ensure that this communication is free from viruses, data corruption, and unauthorized alteration. Bentley Systems does not accept liability for any damages that may be incurred as a result of this or any communication by email\n\n\n[https://cdn2.webdamdb.com/220th_sm_EdpYPzNrja101cmW.jpg?1691764309]\n"}]}