On Mon, Nov 23, 2015 at 08:03PM, Raul Kripalani wrote: > On Mon, Nov 23, 2015 at 3:13 AM, Konstantin Boudnik <c...@apache.org> wrote: > > > Thanks! I already have sent email to the board where this discussion is > > going > > right now. Hopefully, this ban will be lifted soon. > > > > Nice, thanks, Cos! Please keep us informed of their progress on protecting > branches. Maybe repos could have a special branch: .protection with a file > protected_branches.txt, where the project lists which heads should be > protected. The Git server would need a hook to check whether a given branch > deletion is permitted or not, based on that file.
Going into extreme here, if the file is hosted in the repo itself, then an attacker can modify it and then wipe out some branches, if desired. Perhaps, forbidding all tags and branches with keyword release in them might solve the issue. Will see. Cos > > *Raúl Kripalani* > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > Messaging Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk
signature.asc
Description: Digital signature
