my bad, all working now.
On Thursday, May 21, 2015 at 1:22:10 PM UTC-4, Aaron Boxer wrote:
>
> Actually, it *is* a gitlab problem.
>
> It looks like gitlab only accepts the ruby shebang at the top of the
> custom hook file.
>
> #!/bin/sh causes an error, while #!/usr/bin/env ruby does not.
>
>
Actually, it *is* a gitlab problem.
It looks like gitlab only accepts the ruby shebang at the top of the custom
hook file.
#!/bin/sh causes an error, while #!/usr/bin/env ruby does not.
On Thursday, May 21, 2015 at 11:20:59 AM UTC-4, Aaron Boxer wrote:
>
> This turned out to be an issue wit
This turned out to be an issue with the hook files themselves.
Not a gitlab problem.
On Wednesday, May 20, 2015 at 9:57:42 AM UTC-4, Aaron Boxer wrote:
>
> Hello,
> I have a brand new gitlab install via the omnibus package, and I am trying
> to set up custom hooks.
> In my bare repo folder, I
