Google Git
Sign in
gerrit / gerrit / 3a5019e15ec5a92b0bb854e7c940142a0e3793b9
commit3a5019e15ec5a92b0bb854e7c940142a0e3793b9[log] [tgz]
authorKasper Nilsson <kaspern@google.com>Fri Oct 19 10:48:20 2018 -0700
committerKasper Nilsson <kaspern@google.com>Fri Oct 19 10:48:20 2018 -0700
tree264c2f9f9c3fa02d72dc31d6432d0990b2400a58
parentefc6ac890509eff1c82a6d3b0c572530a48c2b16 [diff]
Add gr-embed-dashboard element

In Polymer 1.x, the Shadow DOM polyfill requires using the Polymer.dom
API to achieve distribution. There is no way to notify a DOM mutation
happened after the fact. So, when embedding Polymer 1.x elements inside
an app that is not itself a Polymer app, placing arbitrary content
inside a <slot> is not possible.

This element is intended to be a workaround for the duration of
PolyGerrit's existence on Polymer 1.x to allow for slotting of the
<gr-create-change-help> element into the "empty-outgoing" slot of the
<gr-change-list>.

Change-Id: I32a5031df6fff10e3c441ecdf87c7b50d2073e34
3 files changed
tree: 264c2f9f9c3fa02d72dc31d6432d0990b2400a58
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. gerrit-gwtdebug/
  6. gerrit-gwtui/
  7. gerrit-gwtui-common/
  8. gerrit-plugin-gwtui/
  9. java/
  10. javatests/
  11. lib/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. proto/
  17. resources/
  18. tools/
  19. webapp/
  20. .bazelproject
  21. .bazelrc
  22. .editorconfig
  23. .git-blame-ignore-revs
  24. .gitignore
  25. .gitmodules
  26. .mailmap
  27. .pydevproject
  28. BUILD
  29. COPYING
  30. INSTALL
  31. README.md
  32. SUBMITTING_PATCHES
  33. version.bzl
  34. WORKSPACE
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

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.