16aad55298
The TC confirmed that creating tags (or branches) for repositories in official deliverables should be handled by the release management team through the openstack/releases repository. Yet some ACLs still allow for direct tagging or creating references by some other teams, which can cause process disruption. This removes tagging and branch-creating rights for official deliverables that are already handled by the release management team, or which never released in the past. The tool that generated this patch (and contains the list of remaining team and repository exceptions to the rule) will be posted to the releases repository. Depends-On: https://review.openstack.org/557737 Change-Id: I9feea4a59fccec940a36a7953d35a6f734d86582
28 lines
875 B
Plaintext
28 lines
875 B
Plaintext
[access "refs/for/refs/*"]
|
|
pushMerge = group neutron-release
|
|
|
|
[access "refs/heads/*"]
|
|
abandon = group neutron-vpnaas-core
|
|
label-Code-Review = -2..+2 group neutron-vpnaas-core
|
|
label-Verified = -1..+1 group neutron-ci
|
|
label-Workflow = -1..+1 group neutron-vpnaas-core
|
|
|
|
[access "refs/heads/stable/*"]
|
|
abandon = group Change Owner
|
|
abandon = group Project Bootstrappers
|
|
abandon = group neutron-stable-maint
|
|
exclusiveGroupPermissions = abandon label-Code-Review label-Workflow
|
|
label-Code-Review = -2..+2 group Project Bootstrappers
|
|
label-Code-Review = -2..+2 group neutron-stable-maint
|
|
label-Code-Review = -1..+1 group Registered Users
|
|
label-Workflow = -1..+0 group Change Owner
|
|
label-Workflow = -1..+1 group Project Bootstrappers
|
|
label-Workflow = -1..+1 group neutron-stable-maint
|
|
|
|
[receive]
|
|
requireChangeId = true
|
|
requireContributorAgreement = true
|
|
|
|
[submit]
|
|
mergeContent = true
|