Add some actual sphinx documentation. This is basically the README
split up into sections. Once this is actually published somewhere,
we can remove some of the content from the README and link to an
on-line reference instead.
Change-Id: I25e5ff842e94a5a05aa62c164952df93efc49e98
This feature detects when Gertty is about to upload a review with
a positive vote after someone else has left a negative vote while
Gertty was offline. This prevents a situation where it appears
a user is ignoring negative feedback from others. The local user
is alerted and has the option to re-evaluate their review before
proceeding.
Change-Id: I838acaae6d12a2f8557bfd5a16837784c97c031a
The example configuration for gerrit-review.googlesource.com is also
applicable to other Gerrit instances running at googlesource.com, for
example:
android-review.googlesource.com
gwt-review.googlesource.com
Make the example generic, rather than specific to gerrit-review.
Change-Id: I761db4228aa23e92e57751f5ecbdf721c992065d
Note that Gertty is for all Gerrits, not just OpenStack's, and so
should not assume any OpenStack-specific configuration.
Change-Id: I3f49c7c6589c136785f7d1d698a6dab16dbf0d35
For our friends who find things on github, having a file called
CONTRIBUTING.rst is helpful, as it displays as instructions (that
likely no one will read) in the pull request create screen.
Change-Id: Ifcb28600ccc8919a298639c018f6b49eddb7f4ee
To support commentlinks, palettes, custom dashboards and other
potential future enhancements, we'll need a config file that can
express complex data structures. Change from configparser to yaml,
adding dependencies on pyyaml and voluptuous for validation.
Change-Id: I670eed0cee1b15aa35d0fa9aea0996603ae08444
James E. Blair