Consider this email my +1 on all of them :)

-Joan

On 01/12/2020 10:54, Glynn Bird wrote:
> I've made a start with these PRs:
> 
> https://github.com/apache/couchdb/pull/3285
> https://github.com/apache/couchdb-fauxton/pull/1302
> https://github.com/apache/couchdb-docker/pull/193
> https://github.com/apache/couchdb-pkg/pull/75
> https://github.com/apache/couchdb-helm/pull/47
> https://github.com/apache/couchdb-documentation/pull/609
> 
> 
> On Mon, 30 Nov 2020 at 19:12, Glynn Bird <glynn.b...@gmail.com> wrote:
> 
>> I will. I did start to look at this then got sidetracked. I'll look this
>> week.
>>
>> On Mon, 30 Nov 2020 at 19:01, Joan Touzet <woh...@apache.org> wrote:
>>
>>> Glynn, might you find time to work on this this week? I just noticed
>>> that `main` isn't protected on couchdb-documentation, which is a bad
>>> thing.
>>>
>>> If not I'll try and do it myself.
>>>
>>> -Joan
>>>
>>> On 09/11/2020 12:23, Joan Touzet wrote:
>>>> I think I just heard you volunteer to do the PRs on the repos you
>>>> mentioned below! ;)
>>>>
>>>> I'd leave off www, this isn't something where we need the multi-step
>>>> process.
>>>>
>>>> -Joan
>>>>
>>>> On 09/11/2020 03:55, Glynn Bird wrote:
>>>>> It turns out that branch protection doesn't require Infra intervention,
>>>>> there's a bunch of configuration flags that can be switched on via the
>>>>> .asf.yaml file:
>>>>>
>>> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-BranchProtection
>>>>>
>>>>> An simple configuration example would be:
>>>>>
>>>>> github:
>>>>>   protected_branches:
>>>>>     main
>>>>>
>>>>> On Thu, 5 Nov 2020 at 11:59, Glynn Bird <glynnb...@apache.org> wrote:
>>>>>
>>>>>> Created Infra ticket
>>> https://issues.apache.org/jira/browse/INFRA-21076
>>>>>>
>>>>>> On Wed, 4 Nov 2020 at 16:48, Glynn Bird <glynn.b...@gmail.com> wrote:
>>>>>>
>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>>
>>
> 

Reply via email to