WebMay 31, 2024 · $ git branch master * project/feature_name $ git checkout -b project/feature_name/add_hoge fatal: cannot lock ref 'project/feature_name/add_hoge': 'project/feature_name' exists; cannot … WebApr 4, 2016 · $ git fetch error: Cannot lock ref 'refs/remotes/origin/helen/study-infra': 'refs/remotes/origin/helen' exists; cannot create 'refs/remotes/origin/helen/study-infra' ! [ new branch] helen/study-infra - > origin/helen/study-infra (unable to update local ref) error: some local refs could not be updated; try running 'git remote prune origin' to …
Git config -global init.defaultBranch: Error cannot lock ref
Webremote: error: cannot lock ref 'refs/heads/mybranch': 'refs/heads/mybranch/environment-variables' exists; cannot create 'refs/heads/mybranch' To … WebOct 16, 2024 · Solution: This error can be resolved in different ways but understanding your environment will help. In my case, I had to set git config --global init.defaultBranch main as suggested in “line 18” in the image above. The default branch’s name is main, not master. git config --global init.defaultBranch main shiny panzerglas
git pull error :error: remote ref is at but expected
WebJun 13, 2024 · In my case it showed remote branches but did NOT have origin/HEAD. In that event you can simply do git remote set-head origin main where "main" is the name of your primary (head) branch. Running git branch -r again now shows origin/HEAD -> origin/main and the warning goes away. Some relevant discussion here. WebThe message is: "error: cannot lock ref ... unable to update local ref". If I click Close, wait a few seconds, and click Pull again, it works. I assume this is because Sourcetree's … WebSep 27, 2024 · You need to update the reference using following Git command on Git bash: $ git update-ref -d refs/remotes/origin/[locked branch name] then pull using $git pull … shiny pants black