Just to follow up on this.. for ORM I went ahead and protected master, 5.0, 4.3 and 4.2 branches.
On Tue, Nov 24, 2015 at 10:33 AM Steve Ebersole <st...@hibernate.org> wrote: > This has always made me nervous ever since it happened a few times > inadvertently after first moving to git. Thanks for pointing out that > they finally added support for that. > > For reference... > https://github.com/blog/2051-protected-branches-and-required-status-checks > > On Tue, Nov 24, 2015, 10:24 AM andrea boriero <drebor...@gmail.com> wrote: > >> +1 >> >> On 24 November 2015 at 15:58, Sanne Grinovero <sa...@hibernate.org> >> wrote: >> >> > Hi all, >> > GitHub now provides an option to: >> > - prevent pushing with the "force" option to a specific branch >> > - prevent people to delete a specific branch >> > >> > Considering our workflow and also to prevent user mistakes, I think we >> > should enable them on the reference repositories (the ones in >> > github.com/hibernate ). >> > >> > I did enable this for Hibernate Search. If someone has good reason to >> > want delete a branch or push with "force" it's just two clicks away to >> > disable it.. at least I feel confident against unintentional mistakes. >> > >> > Thanks, >> > Sanne >> > _______________________________________________ >> > hibernate-dev mailing list >> > hibernate-dev@lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
