commit | 4bf16089679b6bb48c9b812e60510fe0f55e48b0 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Wed Aug 07 14:00:29 2019 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Mon Aug 12 09:19:40 2019 +0200 |
tree | fddd224b31911b54bea33f0558d1a40b13c6d7be | |
parent | 46163a82f8d2efb69c3bb54bab6c2f904dadad44 [diff] |
PrologRuleEvaluator: Remove unneeded check for closed changes PrologRuleEvaluator#evaluate() is only used from PrologRule#evaluate(ChangeData, SubmitRuleOptions) which implements the SubmitRule interface. SubmitRules are only invoked from SubmitRuleEvaluator. SubmitRuleEvaluator checks the change state and whether closed changes are allowed before invoking the submit rules. If closed changes are not allowed and the change is closed SubmitRuleEvaluator returns a submit record with status SubmitRecord.Status.CLOSED and the submit rules are not invoked. This means PrologRuleEvaluator#evaluate() doesn't need to the same check again as it is never invoked if this is the case. If this check would be needed all other implementations of SubmitRule would need to do the same, but none of them does. This is part of an effort to eliminate the passing of SubmitRuleOptions into the submit rules. The SubmitRuleOptions contain mostly Prolog-specific settings and are only used by the PrologRule. All other implementation of SubmitRule ignore the options, hence it would be cleaner to remove them from the SubmitRule interface. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I453b575b6aaf22b335cd3d7fa89df662208abf3b
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 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.