It will only mask force-push to other branches. Better restrict access for right people for right repos.
On Saturday, September 12, 2015 at 5:33:55 PM UTC+3, ogondza wrote: > > It seems that Github started providing "Protected branches"[1] > functionality for free. Is this the right time to protect core's master > branch and suggest maintainers to do the same with plugins? Putting this > as a topic on governance meeting agenda. > > [1] > https://github.com/blog/2051-protected-branches-and-required-status-checks > > -- > oliver > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb1d87d7-f3dd-46c8-abc1-3e65b3500bed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
