Limit the number of paths that are included in change messages

We must ensure that the change message, that is posted on review and in
which we include the approved files, doesn't grow too big for large
changes that touch many files. This is why we limit the number of paths
that are included in the change message. By default we include at most
100 paths, but we allow to configure this limit.

Example change message if the limit is exceeded:
"By voting Code-Review+1 the following files are now code-owner
approved by John Doe:
* bar/baz.foo
* bar/foo.baz
(2 more files)"

By setting the limit to 0, including affected paths into change messages
can also be disabled.

Change-Id: I5cbaec24ef54973f3dfea7e05091b80d5f9df369
Signed-off-by: Edwin Kempin <ekempin@google.com>
9 files changed
tree: c16e37f4c0f0d9932f3ed5e5da67ae6d7676c260
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md