commit | 14fd203c4bcb296607b784146c1c4ae6a86e03fa | [log] [tgz] |
---|---|---|
author | Dmitrii Filippov <dmfilippov@google.com> | Tue Feb 25 16:56:07 2020 +0100 |
committer | Dmitrii Filippov <dmfilippov@google.com> | Tue Mar 17 10:09:20 2020 +0000 |
tree | af3f42d72510687551d5890cfa8ec1c893a2d153 | |
parent | b51a20dfd82b229d8d6a5fb14c92c9fd792086fd [diff] |
The tool to convert polygerrit code to es6 modules This is a temporary change. It is reverted here https://gerrit-review.googlesource.com/c/gerrit/+/258560 The entrypoint is the es6-modules-converter.sh script. The script creates(or updates) 2 changes on top of this change: 1. Change to rename all .html files (except tests) to .js files 2. Change to convert polygerrit source code to es6 modules. Important: the tool works only on linux. Doesn't work on mac. How to use: 1. Rebase the relation chain to the latest master (up to and including this change) 2. Checkout this change 3. Run the tool: a) If you run it for the first time (or if you want to create completely new change) ./es6-modules-converter b) If you want to update existing change: ./es6-modules-converter --rename-change-id .... --convert-change-id ... Example: ./es6-modules-converter.sh \ --rename-change-id Ic078c03c9ead018c80142ce1976d7192cb631964 \ --convert-change-id I0c447dd8c05757741e2c940720652d01d9fb7d67 Note: You can see some errors from polymer-modulizer - it is not an actual error. 3. If the tool completes successful, push changes. If you have any error - fix them and repeat starting from the step 1 or 2. 4. Rebase https://gerrit-review.googlesource.com/c/gerrit/+/258560 on top of the created/updated change. Change-Id: Ib186e2d28cd5eba234f65f94b9afa8fa50502515
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.