Allow abandoning/submitting a change when it exceeds maxUpdates
Without this behavior, a change that exceeds maxUpdates is completely
wedged and can't be touched at all. Now, a user can at least abandon a
change with a message about why the change appears stuck. Similarly, a
change can also be pushed directly to a branch bypassing review, and
subsequently marked as merged.
Change-Id: I7db2c535549b4b6fadd74a012d2730a2d18a0012
diff --git a/Documentation/config-gerrit.txt b/Documentation/config-gerrit.txt
index a4e0229..ee02e1b 100644
--- a/Documentation/config-gerrit.txt
+++ b/Documentation/config-gerrit.txt
@@ -1225,6 +1225,13 @@
its contents into memory, so changes with arbitrarily many updates may cause
high CPU usage, memory pressure, persistent cache bloat, and other problems.
+
+The following operations are allowed even when a change is at the limit:
+* Abandon
+* Submit
+* Submit by push with `%submit`
+* Auto-close by pushing directly to the branch
+* Fix with link:rest-api-changes.html#fix-input[`expect_merged_as`]
++
By default 1000.
[[change.replyLabel]]change.replyLabel::
