Clarify rename documentation

Renames a treated as deletion at old path + creation at new path. This
is why for renames code owner approvals are required for the old and the
new path. This reasoning wasn't very clear in the documentation.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I075dd4647fb4070579cfb9dee063bea53d722c1d
1 file changed
tree: b6ff6883d090e787634768ceb66851936c301ffa
  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