|author||Tiago Quelhas <firstname.lastname@example.org>||Tue May 04 12:08:29 2021 -0700|
|committer||Tiago Quelhas <email@example.com>||Tue May 04 19:14:06 2021 +0000|
Add a dummy export statement to files imported as ES modules. Inside Google, we are making it a requirement for files that are imported using ES syntax to be "marked" with an import or export statement. Change-Id: I2c137f228bdd5aa72c8f6b3f8bf1c7a9d5579eb1
This plugin provides a unified experience for checkers (CI systems, static analyzers, etc.) to integrate with Gerrit Code Review.
When upgrading the plugin, please use init:
java -jar gerrit.war init -d site_path
More details about “init” in https://gerrit-review.googlesource.com/Documentation/pgm-init.html
To run UI tests here will need install dependencies from both npm and bower.
npm run wct-test should take care both for you, read more in
You will need
polymer-bridges which is a submodule you can clone from: https://gerrit-review.googlesource.com/admin/repos/polymer-bridges
bazel build gr-checks:gr-checks
gerrit/plugins/checks/folder and it will automatically served at
http://localhost:8081/plugins_/checks/(no need to pass it to --plugins flag)
If your plugin is already enabled, then you can block it and then inject the compiled local verison.
See more about how to use dev helper extension to help you test here: https://gerrit.googlesource.com/gerrit-fe-dev-helper/+/master