Add new copy votes policy for merge commits

Adds new 'copyAllScoresOnMergeFirstParentUpdate' vote policy. This
policy allows to carry over votes on "merge commit rebase". This meas
when only first (left parent) changes and rest of parent(s) stays the
same.

Such policy is useful for changes that are merge commit of feature
branches that tracks destination branch. When it is enabled it reduces
the overhead of CI and human reviews on merge commits that only
incorporate newer changes from destination branch in next patch set.

Change-Id: I02062544608546498d9605c628bc1b7a0386e91a
Signed-off-by: Dariusz Luksza <dariusz@luksza.org>
This commit is contained in:
Dariusz Luksza
2016-01-29 12:06:20 +01:00
parent 6f86343193
commit cedbbee78e
7 changed files with 69 additions and 3 deletions

View File

@@ -246,6 +246,22 @@ forward when a new patch set is uploaded. This can be used to enable
sticky approvals, reducing turn-around for trivial cleanups prior to
submitting a change. Defaults to false.
[[lable_copyAllScoresOnMergCommitFirstParentUpdate]]
=== `label.Label-Name.copyAllScoresOnMergeCommitFirstParentUpdate`
This policy is useful if you don't want to trigger CI or human
verification again if your target branch moved on but the feature
branch being merged into the target branch did not change. It only
applies if the patch set is a merge commit.
If true, all scores for the label are copied forward when a new
patch set is uploaded that is a new merge commit which only
differs from the previous patch set in its first parent. The
first parent would be the parent of the merge commit that is part
of the change's target branch, whereas the other parent(s) refer to
the feature branch(es) to be merged.
Defaults to false.
[[label_copyAllScoresOnTrivialRebase]]
=== `label.Label-Name.copyAllScoresOnTrivialRebase`