Indeed, you'll need shell+possibly sudo access on the server to set up/edit
those custom hooks.

cheers,
Thomas


On Thu, Aug 30, 2012 at 12:11 AM, Trevor <tre...@fea.st> wrote:

> Thanks Thomas, very cool! Between this and LDAP I think it is time for me
> to upgrade.
>
> If those are global then I take it they are not per-repository, and I
> would also need shell access to the server to edit them? I am trying to let
> our project leads enforce code freeze on certain branches.
>
> Cheers,
> Trevor
>
>
> On Tuesday, 28 August 2012 23:31:52 UTC-7, Thomas Kjeldahl Nilsson wrote:
>
>>
>> Sure,
>>
>> we added custom, global serverside git hooks this summer. These hooks are
>> global and are, when enabled, called after Gitorious runs its own custom
>> hooks.
>>
>> I'm going to write up a description of this for our blog soon (clean
>> forgot to announce this over the summer!) but you can just jump in and set
>> them up right now.
>>
>> Check out the doc/instructions within these files:
>>
>> /data/hooks/custom-pre-**receive.sample
>> /data/hooks/custom-post-**receive.sample
>> /data/hooks/custom-update.**sample
>>
>> cheers,
>> Thomas
>>
>>
>>
>> On 08/29/2012 06:47 AM, Trevor wrote:
>>
>> We'd also be interested in this. Currently working on controlling push
>> based on branch.
>>
>>  Regards,
>> Trevor
>>
>> On Monday, 12 December 2011 17:10:50 UTC-8, Mike Murray wrote:
>>>
>>> Has anything changed in the last year that would make it easier/safer to
>>> add in our own custom logic for server-side denial of pushes? Or is the
>>> above discussion the only known potential workaround?
>>>
>>>  Thanks,
>>>
>>>  Mike Murray
>>>
>>  --
>> To post to this group, send email to gito...@googlegroups.com
>>
>> To unsubscribe from this group, send email to
>> gitorious+...@**googlegroups.com
>>
>>
>>
>> --
>> best regards,
>> Thomas Kjeldahl Nilssonhttp://gitorious.com
>>
>>

-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Reply via email to