[Pulp-dev] PUP-3: Proposal to change our git workflow

[Brian Bouterse]

Yes we should enable branch protection to prevent all pushes using that
script. That is one of the main benefits that accepting this pup would
allow (I think).

On Fri, Jun 2, 2017 at 10:48 AM, Michael Hrivnak <mhrivnak at redhat.com>
wrote:

> We already have this script to automatically set branches as protected:
>
> https://github.com/pulp/devel/blob/master/scripts/protect-branches.py
>
> And it could easily disable push also.
>
> On Fri, Jun 2, 2017 at 10:44 AM, Patrick Creech <pcreech at redhat.com>
> wrote:
>
>> On Fri, 2017-06-02 at 16:21 +0200, Ina Panova wrote:
>> > That's correct, we need not to forget to set the new branch as
>> protected.
>> >
>>
>> This can be included in the process for creating new .y releases to
>> ensure it's done at creation
>> time.
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
>>
>
>
> --
>
> Michael Hrivnak
>
> Principal Software Engineer, RHCE
>
> Red Hat
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170602/5ab5dd37/attachment.htm>