Go to file
?ngel ?lvarez Serra ae9644e123 workarround to work with public google account, needs time to refactor and solved correctly 2013-09-12 13:02:43 +02:00
hgreview workarround to work with public google account, needs time to refactor and solved correctly 2013-09-12 13:02:43 +02:00
CHANGELOG prepare for 0.3 release 2012-09-27 22:34:22 +02:00
COPYRIGHT Initial import 2011-03-11 00:37:48 +01:00
INSTALL Initial import 2011-03-11 00:37:48 +01:00
LICENSE Initial import 2011-03-11 00:37:48 +01:00
README Update readme according last commit 2013-06-03 17:22:18 +02:00
setup.py prepare for 0.3 release 2012-09-27 22:34:22 +02:00
test-hgreview.t Remove review_id file on commit 2012-09-27 22:14:17 +02:00

README

hgreview
========

Mercurial extension to work with rietveld code review.

It was inspired by the hg nested extension.

This extension allow to upload to the rietveld code review website, creating a
new issue and remembering its ID for future patches.

See `hg help review` for the complete list of commands.

Options
-------

-r VALUE         Add reviewers
-i VALUE         Issue number. Defaults to new issue
-m VALUE         Codereview message
--rev VALUE      Revision number to diff against
--send_email     Send notification email to reviewers
--id             Output issue id
--url            Output issue URL
--fetch          Fetch patch and apply to repository

.hgrc options
-------------

In the review section of the .hgrc file you can specify some default
information:

servers
    URL/s of the rietveld instance/s to use. Add in list format although if only one.
    Account type/s for authentication either 'GOOGLE' or 'HOSTED'. 

    If you have a special port add in the URL
    e.g.:
        http://codereview.dom1.cat username account_type
        http://codereview.dom2.org:8000 username account_type


host_header
    Alternate hostname to use in the `Host:` header


cc_header
    Comma separated value of username / email in CC of the review

send_email
    A boolean to indicate if the rietveld instance should or not send emails
    after the review has been submitted