Re: Git protected branches

I don't think INFRA extends such admin privileges to projects. I think this is how Gitbox is working. But if we want PMC/projects want to have more privileges, that might require broader discussions in the ASF. - Sijie On Fri, Jul 14, 2017 at 3:13 PM, Enrico Olivelli wrote: > Yes Flavio, > it i

Re: Git protected branches

Yes Flavio, it is a pity that we cannot ever see in readonly mode the actual configuration. If you look at the issue, the operator attached a screenshot in order to let me see the actual configuration Maybe as PMC you or at least Sijie can ask for more privileges -- Enrico 2017-07-14 9:10 GMT+02

Re: Git protected branches

It's kind of odd that we have to go through infra to do this. Such a configuration feels like should be under the control of committers or at least the PMC. Thanks for doing it in any case, Enrico. -Flavio > On 13 Jul 2017, at 01:55, Jia Zhai wrote: > > 👍 > > On Thu, Jul 13, 2017 at 5:34 AM

Re: Git protected branches

👍 On Thu, Jul 13, 2017 at 5:34 AM, Venkateswara Rao Jujjuri wrote: > Awesome. !! > > On Tue, Jul 11, 2017 at 6:06 AM, Enrico Olivelli > wrote: > > > The ticket has been closed. > > The protection is on > > > > -- Enrico > > > > 2017-07-07 11:22 GMT+02:00 Enrico Olivelli : > > > > > > > > > > >

Re: Git protected branches

Awesome. !! On Tue, Jul 11, 2017 at 6:06 AM, Enrico Olivelli wrote: > The ticket has been closed. > The protection is on > > -- Enrico > > 2017-07-07 11:22 GMT+02:00 Enrico Olivelli : > > > > > > > 2017-07-07 1:51 GMT+02:00 Sijie Guo : > > > >> +1 for disable force push to master > >> > > > > >

Re: Git protected branches

The ticket has been closed. The protection is on -- Enrico 2017-07-07 11:22 GMT+02:00 Enrico Olivelli : > > > 2017-07-07 1:51 GMT+02:00 Sijie Guo : > >> +1 for disable force push to master >> > > > this is the issue: > https://issues.apache.org/jira/browse/INFRA-14535 > > I will send updates > >

Re: Git protected branches

2017-07-07 1:51 GMT+02:00 Sijie Guo : > +1 for disable force push to master > this is the issue: https://issues.apache.org/jira/browse/INFRA-14535 I will send updates - Enrico > > On Thu, Jul 6, 2017 at 1:16 PM, Enrico Olivelli > wrote: > > > Other thoughts? > > If there is no objection I w

Re: Git protected branches

+1 for disable force push to master On Thu, Jul 6, 2017 at 1:16 PM, Enrico Olivelli wrote: > Other thoughts? > If there is no objection I would like to enable the force push block. Next > week > > Enrico > > Il mar 4 lug 2017, 10:28 Enrico Olivelli ha scritto: > > > 2017-07-04 5:51 GMT+02:00 Ji

Re: Git protected branches

Other thoughts? If there is no objection I would like to enable the force push block. Next week Enrico Il mar 4 lug 2017, 10:28 Enrico Olivelli ha scritto: > 2017-07-04 5:51 GMT+02:00 Jia Zhai : > > Agree to have them protected. > > Currently, seems these branches are not protected, at least ma

Re: Git protected branches

2017-07-04 5:51 GMT+02:00 Jia Zhai : > Agree to have them protected. > Currently, seems these branches are not protected, at least master branch > is not. The merge button is still available even "Jenkins: Maven clean > install — Build finished." in some of PRs >

Re: Git protected branches

Agree to have them protected. Currently, seems these branches are not protected, at least master branch is not. The merge button is still available even "Jenkins: Maven clean install — Build finished." in some of PRs We may first need to make the test st

Git protected branches

Hi, I don't know current configuration but I would like to ensure that our release branches, that is master and branch-xx are 'protected'. I mean at least that 'force push' must be forbidden to everyone. In github it is simple to enable such protection, see https://help.github.com/articles/about-p