Gerrit Code Review - Searching Changes

Amount of time that has expired since the change was last updated with a review comment or new patch set. The age must be specified to include a unit suffix, for example age:2d:

Changes modified before the given TIME, inclusive. Must be in the format 2006-01-02[ 15:04:05[.890][ -0700]]; omitting the time defaults to 00:00:00 and omitting the timezone defaults to UTC.

Changes modified after the given TIME, inclusive. Must be in the format 2006-01-02[ 15:04:05[.890][ -0700]]; omitting the time defaults to 00:00:00 and omitting the timezone defaults to UTC.

Either a legacy numerical ID such as 15183, or a newer style Change-Id that was scraped out of the commit message.

Changes that conflict with change ID. Change ID can be specified as a legacy numerical ID such as 15183, or a newer style Change-Id that was scraped out of the commit message.

Changes originally submitted by USER. The special case of owner:self will find changes owned by the caller.

Changes originally submitted by a user in GROUP.

Changes that have been, or need to be, reviewed by USER. The special case of reviewer:self will find changes where the caller has been added as a reviewer.

Changes that have been, or need to be, reviewed by a user in GROUP.

Changes where SHA1 is one of the patch sets of the change.

Changes occurring in PROJECT. If PROJECT starts with ^ it matches project names by regular expression. The dk.brics.automaton library is used for evaluation of such patterns.

Changes occurring in PROJECT or in one of the child projects of PROJECT.

Changes for BRANCH. The branch name is either the short name shown in the web interface or the full name of the destination branch with the traditional refs/heads/ prefix.

If BRANCH starts with ^ it matches branch names by regular expression patterns. The dk.brics.automaton library is used for evaluation of such patterns.

Changes whose designated topic at upload was TOPIC. This is often combined with branch: and project: operators to select all related changes in a series.

If TOPIC starts with ^ it matches topic names by regular expression patterns. The dk.brics.automaton library is used for evaluation of such patterns.

Changes where the destination branch is exactly the given REF name. Since REF is absolute from the top of the repository it must start with refs/.

If REF starts with ^ it matches reference names by regular expression patterns. The dk.brics.automaton library is used for evaluation of such patterns.

Search for changes whose commit message contains ID and matches one or more of the trackingid sections in the server’s configuration file. This is typically used to search for changes that fix a bug or defect by the issue tracking system’s issue identifier.

Matches changes where the approval score VALUE has been set during a review. See labels below for more detail on the format of the argument.

Changes that match MESSAGE arbitrary string in the commit message body.

Changes that match TEXT string in any comment left by a reviewer.

Matches any change touching file at PATH. By default exact path matching is used, but regular expressions can be enabled by starting with ^. For example, to match all XML files use file:^.*\.xml$. The dk.brics.automaton library is used for the evaluation of such patterns.

The ^ required at the beginning of the regular expression not only denotes a regular expression, but it also has the usual meaning of anchoring the match to the start of the string. To match all Java files, use file:^.*\.java.

The entire regular expression pattern, including the ^ character, should be double quoted when using more complex construction (like ones using a bracket expression). For example, to match all XML files named like name1.xml, name2.xml, and name3.xml use file:"^name[1-3].xml".

Matches any change touching a file containing the path component NAME. For example a file:src will match changes that modify files named gerrit-server/src/main/java/Foo.java. Name matching is exact match, file:Foo.java finds any change touching a file named exactly Foo.java and does not match AbstractFoo.java.

Regular expression matching can be enabled by starting the string with ^. In this mode file: is an alias of path: (see above).

True if there is a draft comment saved by the current user.

Same as is:starred, true if the change has been starred by the current user.

Same as has:star, true if the change has been starred by the current user.

True if this change matches one of the current user’s watch filters, and thus is likely to notify the user when it updates.

True if there is at least one non-zero score on the change, in any approval category, by any user.

True on any change where the current user is the change owner. Same as owner:self.

True on any change where the current user is a reviewer. Same as reviewer:self.

True if the change is either open or submitted, merge pending.

True if the change is a draft.

True if the change is either merged or abandoned.

Same as status:'STATE'.

True if the change has no merge conflicts and could be merged into its destination branch.

True if the change state is either review in progress or submitted, merge pending.

Same as is:reviewed, matches if there is at least one non-zero score on the change, in any approval category, by any user.

Change has been submitted, but is waiting for a dependency.

True if the change is either merged or abandoned.

Change has been merged into the branch.

Change has been abandoned.

Matches changes where there is at least one +2 score for Code-Review. The + prefix is optional for positive score values. If the + is used, the = operator is optional.

Matches changes where there is at least one -2 score for Code-Review. Because the negative sign is required, the = operator is optional.

Matches changes where there is at least one +1 score for Code-Review. Scores of +2 are not matched, even though they are higher.

Matches changes with either a +1, +2, or any higher score.

Matches changes with a +2 code review where the reviewer or group is aname.

Matches changes with a +2 code review where the reviewer is jsmith.

Matches changes with a +1 code review where the reviewer is in the ldap/linux.workflow group.

Matches changes with either a -1, -2, or any lower score.

Matches changes that are ready to be submitted.

Changes that are blocked from submission due to a blocking score.

Matches changes that are visible to USER or to anyone who is a member of GROUP. Here group names may be specified as either an internal group name, or if LDAP is being used, an external LDAP group name. The value may be wrapped in double quotes to include spaces or other special characters. For example, to match an LDAP group: visibleto:"CN=Developers, DC=example, DC=com".

This operator may be useful to test access control rules, however a change can only be matched if both the current user and the supplied user or group can see it. This is due to the implicit is:visible clause that is always added by the server.

Magical internal flag to prove the current user has access to read the change. This flag is always added to any query.

Matches changes that have been starred by USER. The special case starredby:self applies to the caller.

Matches changes that USER has configured watch filters for. The special case watchedby:self applies to the caller.

Matches changes that USER has left unpublished draft comments on. Since the drafts are unpublished, it is not possible to see the draft text, or even how many drafts there are. The special case of draftby:self will find changes where the caller has created a draft comment.

Limit the returned results to no more than CNT records. This is automatically set to the page size configured in the current user’s preferences. Including it in a web query may lead to unpredictable results with regards to pagination.