Document how code owner approvals can be made sticky
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ibe390688091e92e65e30c0ef8d21e38e4754f65d
diff --git a/resources/Documentation/config.md b/resources/Documentation/config.md
index 5f3724c..b67693b 100644
--- a/resources/Documentation/config.md
+++ b/resources/Documentation/config.md
@@ -141,6 +141,10 @@
The configured label must exist for all projects for which this setting
applies (all projects that have code owners enabled and for which this
setting is not overridden).\
+ If the definition of the configured label has [copy
+ rules](../../../Documentation/config-labels.html#label_copyAnyScore)
+ enabled so that votes are sticky across patch sets, also the code owner
+ approvals will be sticky.\
Can be overridden per project by setting
[codeOwners.requiredApproval](#codeOwnersRequiredApproval) in
`@PLUGIN@.config`.\
@@ -363,6 +367,10 @@
The configured label must exist for all projects for which this setting
applies (all child projects that have code owners enabled and for which
this setting is not overridden).\
+ If the definition of the configured label has [copy
+ rules](../../../Documentation/config-labels.html#label_copyAnyScore)
+ enabled so that votes are sticky across patch sets, also the code owner
+ approvals will be sticky.\
Overrides the global setting
[plugin.@PLUGIN@.requiredApproval](#pluginCodeOwnersRequiredApproval) in
`gerrit.config`.\
diff --git a/resources/Documentation/setup-guide.md b/resources/Documentation/setup-guide.md
index f94044f..c662be7 100644
--- a/resources/Documentation/setup-guide.md
+++ b/resources/Documentation/setup-guide.md
@@ -219,6 +219,12 @@
(e.g. change the `Code-Review` label definition to not require a `Code-Review+2`
vote for change submission.
+**NOTE:** Whether code owner approvals are sticky across patch sets depends on
+the definition of the required label. If the label definition has [copy
+rules](../../../Documentation/config-labels.html#label_copyAnyScore) enabled so
+that votes are sticky across patch sets, then also the code owner approvals
+which are based on these votes will be sticky.
+
### <a id="grantCodeOwnerPermissions">5. Grant code owners permission to vote on the label that counts as code owner approval
Code owners must be granted permissions to vote on the label that counts as code
diff --git a/resources/Documentation/user-guide.md b/resources/Documentation/user-guide.md
index 8e98f59..83194b2 100644
--- a/resources/Documentation/user-guide.md
+++ b/resources/Documentation/user-guide.md
@@ -86,6 +86,12 @@
non-code-owner approvals are required and missing, or if further non-code-owner
submit requirements are not fulfilled yet.
+**NOTE:** Whether code owner approvals are sticky across patch sets depends on
+the definition of the required label. If the label definition has [copy
+rules](../../../Documentation/config-labels.html#label_copyAnyScore) enabled so
+that votes are sticky across patch sets, then also the code owner approvals
+which are based on these votes will be sticky.
+
## <a id="codeOwnerOverride">Code owner override
Usually some privileged users, such as sheriffs, are allowed to override the
