|author||Edwin Kempin <email@example.com>||Wed Apr 19 10:38:01 2023 +0000|
|committer||Edwin Kempin <firstname.lastname@example.org>||Wed Apr 19 10:40:43 2023 +0000|
Escape Markdown characters in paths that are posted in change messages The web frontend renders change messages as Markdown. Due to this paths that contain Markdown characters were triggering Markdown formatting. E.g. a file '__foo__.bar' was rendered as '<b>foo</b>.bar'. Fix this by escaping Markdown characters in paths when they are included into change messages. Signed-off-by: Edwin Kempin <email@example.com> Change-Id: Icfd038afd7e80b0d4d53ff7bdbe1518b9d2df82d
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.
For a detailed description of the plugin functionality please refer to the plugin documentation.
IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide.
NOTE: The plugin documentation only renders correctly when the plugin is installed in Gerrit and the documentation is accessed via https:///plugins/code-owners/Documentation/index.html. If you want to read the documentation before installing the plugin, you can find it properly rendered here.
From the root of the gerrit repository.
bazel test //plugins/code-owners/web:karma_test
For testing the plugin with the Gerrit FE Dev Helper the command below builds
bazel build //plugins/code-owners/web:code-owners ln -s bazel-bin/plugins/code-owners/web/code-owners.js polygerrit-ui/app/plugins/
and let the Dev Helper redirect from