9e669e52a4
Currently the value persists only if it's the max or min, and only
when there are no code changes or if it's a trivial rebase.
The behavior we'd like is that the assigned priority should persist
across the series of patch sets, even if there are code changes,
because this label indicates the relative importance of getting eyes
on the review, and is not directly involved in the code being approved.
A -1 Review-Priority ("Branch Freeze"), in addition to being sticky,
will continue to block submission of the patch.
Change-Id: Iee323ab80f9a58bf49827c23934560edfad57bf3
42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
[access]
|
|
inheritFrom = openstack/meta-config
|
|
|
|
[access "refs/heads/*"]
|
|
abandon = group glance-core
|
|
abandon = group glance-reviewbot
|
|
label-Code-Review = -2..+2 group glance-core
|
|
label-Review-Priority = -1..+2 group glance-core
|
|
label-Workflow = -1..0 group glance-reviewbot
|
|
label-Workflow = -1..+1 group glance-core
|
|
|
|
[access "refs/heads/stable/*"]
|
|
abandon = group Change Owner
|
|
abandon = group Project Bootstrappers
|
|
abandon = group glance-stable-maint
|
|
abandon = group stable-maint-core
|
|
exclusiveGroupPermissions = abandon label-Code-Review label-Workflow
|
|
label-Code-Review = -2..+2 group Project Bootstrappers
|
|
label-Code-Review = -2..+2 group glance-stable-maint
|
|
label-Code-Review = -2..+2 group stable-maint-core
|
|
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 glance-stable-maint
|
|
label-Workflow = -1..+1 group stable-maint-core
|
|
|
|
[label "Review-Priority"]
|
|
copyAnyScore = true
|
|
defaultValue = 0
|
|
function = AnyWithBlock
|
|
value = -1 Branch Freeze
|
|
value = 0 No Priority
|
|
value = +1 Important Change
|
|
value = +2 Top Priority / Holds Gate
|
|
|
|
[receive]
|
|
requireChangeId = true
|
|
requireContributorAgreement = true
|
|
|
|
[submit]
|
|
mergeContent = true
|