If running certain commands from SmartGit fails, which work when running from command line, this is usually caused by a different
PATH environment of SmartGit. This happens e.g. when extending the
PATH in files like
~/.bash_profile, ~/.bash_login, and ~/.profile. Because SmartGit is not starting an interactive shell, these files won't be processed. The solution is to specify the
PATH either in a file which will be processed by the system when starting SmartGit (for OSX, see this Stackoverflow answer) or by adding
smartgit.vmoptions, see .
git: 'credential-osxkeychain' is not a git command.