[Nix-dev] Accidental force push to nixpkgs

Kirill Elagin kirelagin at gmail.com
Tue Apr 8 08:34:57 CEST 2014


It might be a good idea to set up a post receive hook that does git pull on
each new revision, so it has all the commits,
and if it detects a force push, it sends an email with last commit's hash
to the list and to the commiter.


--
Кирилл Елагин


On Tue, Apr 8, 2014 at 10:27 AM, Alexander Kjeldaas <ak at formalprivacy.com>wrote:

>
> It is possible to add a post receive hook that sends out a big fat warning.
>
> Alexander
>
>
> On Tue, Apr 8, 2014 at 8:14 AM, Vladimír Čunát <vcunat at gmail.com> wrote:
>
>> On 04/07/2014 07:30 PM, Shea Levy wrote:
>>
>>> I had my remotes set up wrong and accidentally force pushed
>>>
>>
>> I see it happens occasionally... is it possible on GitHub to forbid
>> force-pushes? I don't know about any use case of non-fast-forward pushing
>> on the central repo.
>>
>> Vlada
>>
>>
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20140408/4e139813/attachment.html 


More information about the nix-dev mailing list