Maybe your issue is related to
>> https://gitlab.com/gitlab-org/omnibus-gitlab/issues/406
>>
>
> To me LOAD_PATH didn't seem like cause of the issue, Only rationale I
> could come up with, if it's also chrooted?
>
In pry I did
lp1 = $LOAD_PATH.dup
require 'my/gem'
lp2 = $LOAD_PATH.dup
lp2
On Thursday, 12 March 2015 16:25:22 UTC+2, Achilleas Pipis wrote:
> Maybe your issue is related to
> https://gitlab.com/gitlab-org/omnibus-gitlab/issues/406
>
To me LOAD_PATH didn't seem like cause of the issue, Only rationale I could
come up with, if it's also chrooted?
--
You received
On Wednesday, March 11, 2015 at 6:01:20 PM UTC+2, Saku Ytti wrote:
>
> I believe this use-case applies to custom hooks too, but my use-case is
> modifying gitlab-shell hooks, so not exactly supported.
>
>
> I want hook for all repos, so I'm calling my own class in post-receive,
> this works great
I believe this use-case applies to custom hooks too, but my use-case is
modifying gitlab-shell hooks, so not exactly supported.
I want hook for all repos, so I'm calling my own class in post-receive,
this works great.
However post-receive is not called for 'accept merge request' events, and I
