Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SourceTree issues solved! #196

Closed
florianbachmann opened this issue Mar 7, 2014 · 5 comments
Closed

SourceTree issues solved! #196

florianbachmann opened this issue Mar 7, 2014 · 5 comments
Assignees

Comments

@florianbachmann
Copy link

Hi I solved all my GUI-client issues under OSX!

I added the path of ImageMagick (convert) to post-commit and everything worked flawlessly :-)
One year and these line /usr/local/bin/ prevented me to use the aweseome lolcommits.
thanks :-)

This is my file:

#!/bin/sh

### lolcommits hook (begin) ###
export PATH="/Users/flori/.rvm/rubies/ruby-2.0.0-p195/bin/ruby:/usr/local/bin/:$PATH"
lolcommits --capture
###  lolcommits hook (end)  ###

So maybe, would it be possible to add the path of ImageMagick to post-commit?

@matthutchinson
Copy link
Member

I'll investigate this one further and see if that makes sense, would help us close a tonne of issues around GUI clients 😄

@matthutchinson matthutchinson self-assigned this Aug 10, 2014
@dincho
Copy link

dincho commented Aug 13, 2014

I can confirm that adding the path to "convert" binary (in my case /usr/local/bin) in post-commit script, fix the issues i had in SourceTree

I had this error before: FATAL -- : FATAL: ImageMagick does not appear to be properly installed!

matthutchinson added a commit that referenced this issue Sep 4, 2014
Also, this fix most likely closes many other issues around the same
problem, will try to verify on various clients.
matthutchinson added a commit that referenced this issue Sep 4, 2014
Also, this fix most likely closes many other issues around the same
problem, will try to verify on various clients.
matthutchinson added a commit that referenced this issue Sep 4, 2014
Also, this fix most likely closes many other issues around the same
problem, will try to verify on various clients.
@matthutchinson
Copy link
Member

Now fixed in gem release 0.5.5! (see the CHANGELOG for more details)

gem install lolcommits to get the latest version 👍

@matthutchinson
Copy link
Member

NOTE: After installing the latest version you'll need to lolcommits --disable and then lolcommits --enable again to fix any existing hook already set from an earlier gem install.

If lolcommits --disable fails to remove the hook, try blowing away /path/to/your/repo/.git/hooks/post-commit (or editing that file manually to clean away any existing lolcommit applied hook before trying to enable again).

@florianbachmann
Copy link
Author

yeah :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants