2.3 KiB
xcrun: error: invalid developer path
This is an error occurring only on macOS. It's easy to fix though. Just run the following snippet in the terminal. xcode-select --install See #64 as an example.
Error: spansSync git ENOENT/ Cannot run Git command
This occurs, when the plugin can't find the Git executable. It takes it from the PATH. Head over to Installation to see if everything is properly installed for your platform. If you think everything is correctly set up and the error still occurs try the following:
In case you know where Git is installed, you can set the path under "Custom Git binary path" in the settings. If you don't know where Git is installed, you can try to find it by running the following in the terminal:
Windows
Run where git in the terminal. It should return the path to the Git executable. If it fails, Git is not properly installed.
Linux/MacOS
Run which git in the terminal. It should return the path to the Git executable. If it fails, Git is not properly installed.
Infinite pulling/pushing with no error
That's most time caused by authentication problems. Head over to Authentication
Bad owner or permissions on /home/<user>/.ssh/config
Run chmod 600 ~/.ssh/config in the terminal.
Files in .gitignore aren't ignored
Since the plugin uses the native git installation, I can assure you that if the .gitignore file is properly written and git is correctly used, everything should work.
It's important to note that once a file is committed (or staged) changing the .gitignore doesn't help. You have to delete the file from your repo manually to ignore the file properly:
- Run
git rm --cached <file>in your terminal. The file will stay on your file system. It's just deleted in your repo. - The file should be listed as deleted in
git status - Commit the deletion
- Now any changes to the file are properly ignored.
Cannot run gpg
Error: error: cannot run gpg: No such file or directory
error: gpg failed to sign the data
fatal: failed to write commit object
See Integration with other tools#GPG Signing on how to solve this.
This repository is configured for Git LFS but 'git-lfs' was not found on your path.
See Integration with other tools#Git Large File Storage on how to solve this.