Please make sure all processesĪre terminated then try again. (use "git push" to publish your local commits)įurther pushes might give a File exists error (however, the commit is successfully pushed to remote): $ git pushĮrror: update_ref failed for ref 'refs/remotes/origin/main': cannot lock ref 'refs/remotes/origin/main': Unable to create '/home//.git/refs/remotes/origin/main.lock': File exists.Īnother git process seems to be running in this repository, e.g.Īn editor opened by 'git commit'. Your branch is ahead of 'origin/main' by 1 commit. In a machine with Windows 10 and Windows Subsystem for Linux, if the user has a git repository in a directory managed by Dropbox, the following error might appear when trying to git push a recent commit: warning: unable to unlink '/home//repo/.git/refs/remotes/origin/main.lock': Permission deniedĮrror: update_ref failed for ref 'refs/remotes/origin/main': couldn't set 'refs/remotes/origin/main'Īdditionally, on git status the repository will appear to be ahead of the remote, even while the remote has been updated: $ git status Storing repositories in Dropbox-synced folders should be avoided.
I would just like to document this issue, which arises from an incompatibility between git and cloud syncing services.
0 kommentar(er)
