Config guide: Document the possibility to validate code owner configs externally
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I28d3f6c795ed4af87db35dfa37861ae122456c3d
diff --git a/resources/Documentation/validation.md b/resources/Documentation/validation.md
index d6160d6..b3b6405 100644
--- a/resources/Documentation/validation.md
+++ b/resources/Documentation/validation.md
@@ -20,6 +20,11 @@
etc.) are severe errors and block the submission of all changes for which the
affected configuration files are relevant.
+**NOTE:** It's possible to disable the validation of code owner config files on
+push and setup an [external
+validation](config-guide.html#externalValidationOfCodeOwnerConfigs) by a CI bot
+instead. In this case findings would be posted on the change.
+
All validations are best effort to prevent invalid configurations from
entering the repository, but not all possible issues can be prevented. Doing the
validation is useful since it prevents most issues and also gives quick feedback
