https://github.com/apache/couchdb- main not protected https://github.com/apache/couchdb-fauxton- main not protected https://github.com/apache/couchdb-docker - main not protected https://github.com/apache/couchdb-www - still using master https://github.com/apache/couchdb-pkg - main not protected https://github.com/apache/couchdb-helm - main not protected ...
There are numerous others. I couldn't find an example where the main branch _was_ protected, but in most cases the old master branch was. Glynn On Wed, 4 Nov 2020 at 16:36, Glynn Bird <glynn.b...@gmail.com> wrote: > I'm on it. > > Glynn > > On Wed, 4 Nov 2020 at 16:23, Joan Touzet <woh...@apache.org> wrote: > >> Yes, you'll have to file a ticket with Infra for this. >> >> We probably need to do this on quite a few repos, which unfortunately >> means that we may be forced to write a script to address it. >> >> Would you be willing to volunteer to check and see which ones have >> unprotected main branches - at least for the big 4-5 or so (couchdb, >> docs, fauxton come to mind)? >> >> -Joan >> >> On 04/11/2020 11:13, Glynn Bird wrote: >> > I've published the 9.0.0 release of Nano, the Node.js library for >> CouchDB >> > which features: >> > >> > - request library replaced with axios 👩🔧 >> > - rewritten changes follower 🚿 >> > - fewer dependencies 📉 >> > >> > https://www.npmjs.com/package/nano >> > >> > Thanks to all who helped in the work to build and test this release. >> > >> > While tidying up afterwards I noticed that the new default main branch >> is >> > "unprotected" and the old default ("master") is "protected" so I can't >> > delete it. >> > >> > Is this something Apache Infra would be able to help with? >> > >> > Glynn >> > >> >
