Skip to content

Troubleshooting

Jump to bottom
TomOak edited this page Apr 19, 2023 · 2 revisions

This plugin is based on the assumption that git lock commands work in your terminal, so the first step if something doesn't work is to open it (on Windows for example Windows Key > "cmd"), navigate to your repository, then check if something's wrong by entering this command for example: git lfs locks

   

Here are a few errors we encountered and ideas on how to fix them...

“Cannot unlock file with uncommitted changes”

  • Commit your work, then unlock the file

OR

  • Stash your work, unlock the file, re-apply your stash

   

“You must have admin access to force delete a lock”

  • Ask the repository admin or the owner of the lock to unlock it, if you really need it

   

The Github Login window keeps popping up

“Failed to execute prompt script (exit code 1)”

“git: ‘credential-manager-core’ is not a git command.”

Try Updating Git for Windows (shortcut available in the plugin's preferences)

   

“Error while retrieving locks: exit status 255”

If you’re using SSH authentication, it might be that the command line can’t connect properly:

  • Open the Services window (Windows key > “services” > Enter key), double-click on “OpenSSH Authentication Agent”
  • Set the Startup type to “Automatic” and press “Start” under “Service status”
  • Open a powershell terminal (Windows key > “powershell” > Enter key) and input the following command

ssh-add C:\pathToMySSHFile\id_rsa

SSH files are often located in your user directory, inside the “.ssh” folder

  • Then input the following command

setx GIT_SSH C:\Windows\System32\OpenSSH\ssh.exe

  • Reboot

It might also be another ssh-related problem, in this case open a windows command line, try a git fetch and see what error message is displayed.

   

“Remote "origin" does not support the LFS locking API. Consider disabling it [...]”

   

I need to push changes to the repository even if some files are locked

  • ⚠️It’s a dangerous operation ! The only valid exception to this rule is for cherrypicked commits, which trigger conflicts even if they shouldn’t.
  • You can use the following command in your git repository to disable the verification on push:

git config --local lfs.https://github.com/MyUsername/MyRepository.locksverify false

  • To revert to the original state, use the opposite command:

git config --local lfs.https://github.com/MyUsername/MyRepository.locksverify true

Clone this wiki locally