opendev/gerrit
Code Issues Proposed changes
9fb86732b9
gerrit/polygerrit-ui
History
Andrew Bonventre 882043f905 Move reply from dropdown to dialog 
This makes things more friendly on mobile and doesn’t have
any significant usability difference.
Also size the resize dialog to fit within the screen on mobile.

Bug: Issue 3908
Bug: Issue 3866
Change-Id: I0aac13d47407a5f5b0d53a6efd2602d5c2b7c10c
2016-02-23 15:30:32 +00:00
..
app Move reply from dropdown to dialog 2016-02-23 15:30:32 +00:00
.gitattributes Add the skeleton of a new UI based on Polymer, PolyGerrit 2015-11-09 22:01:28 +00:00
.gitignore Draft comments initial implementation 2015-12-09 12:32:37 -05:00
BUCK Add a preferences pane to the diff view 2016-01-28 20:57:20 +00:00
README.md PolyGerrit: Mention style guide used in the project 2016-02-13 10:45:34 +00:00
run-server.sh Add quick script to run server.go 2015-12-03 13:49:40 -05:00
server.go Add support for html and enabled fields in link configs 2016-01-15 16:06:57 -05:00
wct.conf.js Add the skeleton of a new UI based on Polymer, PolyGerrit 2015-11-09 22:01:28 +00:00

README.md

PolyGerrit

Installing Node.js

# Debian/Ubuntu
sudo apt-get install nodejs-legacy

# OS X with Homebrew
brew install node

All other platforms: download from nodejs.org.

Local UI, Production Data

To test the local UI against gerrit-review.googlesource.com:

./run-server.sh

Then visit http://localhost:8081

Local UI, Test Data

One-time setup:

  1. Install Buck for building Gerrit.
  2. Build Gerrit and set up a local test site.

Run a test server:

buck build polygerrit && \
java -jar buck-out/gen/polygerrit/polygerrit.war daemon --polygerrit-dev -d ../gerrit_testsite --console-log --show-stack-trace

Running Tests

One-time setup:

# Debian/Ubuntu
sudo apt-get install npm

# OS X with Homebrew
brew install npm

# All platforms (including those above)
sudo npm install -g web-component-tester

Run all web tests:

buck test --include web

If you need to pass additional arguments to wct:

WCT_ARGS='-p --some-flag="foo bar"' buck test --no-results-cache --include web

Style guide

We follow the Google JavaScript Style Guide with a few exceptions. When in doubt, remain consistent with the code around you.