[submit-requirement "Code-Review"]
description = A maximum vote from a non-uploader is required for the \
'Code-Review' label. A minimum vote is blocking.
submittableIf = label:Code-Review=MAX,user=non_uploader AND -label:Code-Review=MIN
canOverrideInChildProjects = true
However it seems odd to see that change Owner is able to do a CR+2 for his/her own change
In 2.14 we only had label definition and change owner is not allowed to CR+2 own change.
Is there a way to disallow change owner doing CR+2 on own change?
Please let me know
thanks
Pranab
Please let me know
thanks
Pranab
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/7f3bee93-ea07-44ed-b28d-fdd2dcd1c255n%40googlegroups.com.
On Tue, 28 Mar 2023 at 08:21, Pranab Panda <pra...@pacbell.net> wrote:HiMigrated to 3.7.1 from 2.14 and find something oddChange Owner is able to merge own change by giving a CR+2 !Had to add the submit-requirement check as explained in Documentation to plug this hole.[submit-requirement "Code-Review"]
description = A maximum vote from a non-uploader is required for the \
'Code-Review' label. A minimum vote is blocking.
submittableIf = label:Code-Review=MAX,user=non_uploader AND -label:Code-Review=MIN
canOverrideInChildProjects = true
However it seems odd to see that change Owner is able to do a CR+2 for his/her own change
In 2.14 we only had label definition and change owner is not allowed to CR+2 own change.
Is there a way to disallow change owner doing CR+2 on own change?
Typically the owner is also the uploader, so `user=non_uploader` in the above rule should take care of that. Did you give it a try?
---Ben--
Please let me know
thanks
Pranab
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/7f3bee93-ea07-44ed-b28d-fdd2dcd1c255n%40googlegroups.com.
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/CAEWS%2BaNU71d-a5eRamvNfgc8YOYRkB8eYn%3DyVc_0j5--F-pXsw%40mail.gmail.com.
On Tue, Mar 28, 2023 at 10:38 AM 'Ben Rohlfs' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:On Tue, 28 Mar 2023 at 08:21, Pranab Panda <pra...@pacbell.net> wrote:HiMigrated to 3.7.1 from 2.14 and find something oddChange Owner is able to merge own change by giving a CR+2 !Had to add the submit-requirement check as explained in Documentation to plug this hole.[submit-requirement "Code-Review"]
description = A maximum vote from a non-uploader is required for the \
'Code-Review' label. A minimum vote is blocking.
submittableIf = label:Code-Review=MAX,user=non_uploader AND -label:Code-Review=MIN
canOverrideInChildProjects = true
However it seems odd to see that change Owner is able to do a CR+2 for his/her own change
In 2.14 we only had label definition and change owner is not allowed to CR+2 own change.
Is there a way to disallow change owner doing CR+2 on own change?
Typically the owner is also the uploader, so `user=non_uploader` in the above rule should take care of that. Did you give it a try?Submit requirements only control when a change is submittable, e.g. which votes are required and which votes are ignored.They don't influence which votes the user can apply on the change, so `user=non_uploader` only means that a non-uploader vote is required for submission, but it doesn't prevent the uploader from voting on the own change. Whether voting is possible solely depends on the permissions.If you want to disallow change owners to vote with CR+2 on their own changes you may try to block the CR-label permission for the magic Change Owner group [1]. It may be necessary to block this permission on a parent project [2].HTH-Ben
On Tue, Mar 28, 2023 at 10:38 AM 'Ben Rohlfs' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:On Tue, 28 Mar 2023 at 08:21, Pranab Panda <pra...@pacbell.net> wrote:HiMigrated to 3.7.1 from 2.14 and find something oddChange Owner is able to merge own change by giving a CR+2 !Had to add the submit-requirement check as explained in Documentation to plug this hole.[submit-requirement "Code-Review"]
description = A maximum vote from a non-uploader is required for the \
'Code-Review' label. A minimum vote is blocking.
submittableIf = label:Code-Review=MAX,user=non_uploader AND -label:Code-Review=MIN
canOverrideInChildProjects = true
However it seems odd to see that change Owner is able to do a CR+2 for his/her own change
In 2.14 we only had label definition and change owner is not allowed to CR+2 own change.
Is there a way to disallow change owner doing CR+2 on own change?
Typically the owner is also the uploader, so `user=non_uploader` in the above rule should take care of that. Did you give it a try?Submit requirements only control when a change is submittable, e.g. which votes are required and which votes are ignored.They don't influence which votes the user can apply on the change, so `user=non_uploader` only means that a non-uploader vote is required for submission, but it doesn't prevent the uploader from voting on the own change. Whether voting is possible solely depends on the permissions.If you want to disallow change owners to vote with CR+2 on their own changes you may try to block the CR-label permission for the magic Change Owner group [1]. It may be necessary to block this permission on a parent project [2].HTH-Ben
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/d10beb89-3150-40ff-b21e-26cdf37e1eban%40googlegroups.com.
Please let me know
thanks
Pranab
The Submit requirement labels are not in Sorted order
SmokeTest label can be at the top and Code-Review label at the bottom!Is there any way to get the labels displayed in Sorted alphabetical order?
Please let me knowthanksPranab
Meant to say I addedlabel-Code-Review = deny group Change Ownerbut it didn't help.
I would try this with block instead of deny.
Please let me know
thanks
Pranab