commit | 2b2f3897cf96964f5ef612d98b7cfe8fb7f452f8 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Fri Jan 25 10:34:07 2019 +0100 |
committer | Edwin Kempin <ekempin@google.com> | Tue Jan 29 08:54:42 2019 +0100 |
tree | 21d265fda8f427fdd72c955df8f3a99f3795af77 | |
parent | b746dadf3ee9c6d23681734c9215d513156f4426 [diff] |
Support searching changes which only touch certain file extensions With the current 'extension' search operator it's possible to find a) changes that contain at least one file with the given extension, e.g.: extension:txt b) changes that contain no file with the given extension, e.g.: -extension:txt However sometimes you want to match changes which only contain files of a given extension, e.g. changes that only touch txt files. This can now be done with the new 'only_extensions' search operator, e.g.: only_extensions:txt It is also possible to specify multiple file extensions. E.g. matching changes that only touch txt and jpg files can be done by: only_extensions:jpg,txt By reversing the 'only_extensions' search operator it is possible to match changes that not only touch files with certain extensions, e.g.: -only_extensions:jpg,txt The order and the case in which the extensions are provided to the 'only_extensions' operator don't matter. Also extensions can be specified with or without leading '.' (same as for the 'extension' search operator). Changes that contain files without file extension can be matched by including an empty file extension into the file extension list, e.g.: * changes that only include txt files and files without extension: only_extensions:,txt * changes that only contain files without extension: only_extensions:, only_extensions:"" Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I3d2b978ed455f835d1dad2daa920be0b0ec2ae36
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.