Branches are already protected and can only be written to by committers with
the according rights.
We already do pull requests and reviews.
There is no point to add more complexity and remove flexibility, in case we
need it, from my point of view.
- Markus
> On 30 Jan 2017, at 14:53, Ronny Trommer <ro...@opennms.org> wrote:
>
> Hi Guys,
>
> I would like vote for setting up Review required [1] for protected branches
> like foundation / foundation-2016 / master / develop?
>
> Any thoughts about this?
>
> [1]
> https://help.github.com/articles/about-required-reviews-for-pull-requests/
> <https://help.github.com/articles/about-required-reviews-for-pull-requests/>
>
> Greetings Ronny
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org!
> http://sdm.link/slashdot_______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this
> page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel