Git/Reviewers


 * If you are looking for a list of people that could review your patch, please see Developers/Maintainers.

This is a page where people can register to be automatically added as reviewer to newly opened changes in Gerrit depending on specific conditions. After registering here, reviewer-bot will add you as reviewer to every change that matches the project and file filter.

Gerrit supports a similar feature by itself (including filtering by modified file name and words appearing in commit message), see Gerrit/watched projects and https://gerrit.wikimedia.org/r/settings/projects.

How to add yourself
Each project has a header with the gerrit project name, followed by a list of people (using Template:Gerrit-reviewer), for example:

=== test/mediawiki/extensions/examples ===

The  parameter can be used to filter for changes in specific files:

* will watch for changes where a file with 'i18n' in the name is changed, while

* will watch for changes in the includes/specials directory. You can test the regexp using with flags re.I and re.S, and method 'search' (rather than 'match'). The &lt;nowiki&gt; tags are suggested but only required when the regexp contains characters that interfere with template parsing (e.g. | and }}).

An optional  parameter makes the bot only mark changes where the   matches all the changed files:

* This is useful since review scores apply to the whole changeset, rather than parts of it, so users that are comfortable with reviewing only a subsection of the changes wouldn't be able to review the whole patchset. For instance, front-end changes often touch both CSS and JavaScript files. A user who is confident about his CSS knowledge but not so much about his JavaScript ones can use  to restrict reviews attributed to them to those that only touch CSS files.

Listen to repository groups
Projects are matched based on unix filename matching as implemented in the fnmatch module. The idea is to set a file_regexp, which filters changesets by changed files instead of repository.