Actually found out it is a duplicate of #26 which was submitted already in December 2014.

Please consider merging this — otherwise integrations will break.

Coverage decreased (-7.73%) to 70.39% when pulling b79c91e on martintajur:patch-1 into e640075 on GeneralScripting:master.

Today was the day, and they really did it. 👊
I'll implement a quick fix by now.
Let me know if there is something I can help with.

thnsk

I see that there is no update to the main release, and my system just not working with Pipedrive anymore ... Can anyone advise how should I use the pull request version instead?

@tzahif1, This what I am doing:
I forked the project, and made the changes right on master, then I am using my own repo until the official gem gets update.

On my gem file replaced the prev gem line with this one:
gem 'pipedrive-ruby', :git => 'git://github.com/ronniebermejo/pipedrive-ruby.git'

(I know you can point to any commit/branch from a gem line but not remember how to doi it right now)

Thanks, I realized it earlier and did exactly like you :) it works nice so far.
I am just do not understand why such a simple fix could not be fixed in the main project branch.

On May 12, 2015, at 6:42 PM, Ronnie Bermejo notifications@github.com wrote:

@tzahif1 https://github.com/tzahif1, This what I am doing:
I forked the project, and made the changes right on master, then I am using my own repo until the official gem gets update.

On my gem file replaced the prev gem line with this one:
gem 'pipedrive-ruby', :git => 'git://github.com/ronniebermejo/pipedrive-ruby.git'

(I know you can point to any commit/branch from a gem line but not remember how to doi it right now)

—
Reply to this email directly or view it on GitHub #33 (comment).