1b20aa2df3
If we upload source tarballs to PyPI instead of eggs, then the man pages actually work. However, this means that the installer has to run setup.py. Using sphinx, while slighly nicer from a dev perspective, means we have to then require that people installing git-review also install sphinx, which is a bit overkill given the size of the man page. This change, and a change to the release process of not uploading eggs to PyPI should finall get git review --help to work. Change-Id: I29b07667127a9ec5c241b7e1fc5a3960dd2a6b63 |
||
|---|---|---|
| .gitignore | ||
| .gitreview | ||
| AUTHORS | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.md | ||
| git-review | ||
| git-review.1 | ||
| setup.py | ||
README.md
git-review
A git command for submitting branches to Gerrit
git-review is a tool that helps submitting git branches to gerrit for review.
Setup
git-review, by default, looks for a git remote called gerrit, and submits the current branch to HEAD:refs/for/master at that remote.
If the "gerrit" remote does not exist, git-review looks for a file called .gitreview at the root of the repository with information about the gerrit remote. Assuming that file is present, git-review should be able to automatically configure your repository the first time it is run.
Usage
Hack on some code, then:
git review
If you want to submit that code to a branch other than "master", then:
git review branchname
If you want to submit to a different remote:
git review -r my-remote
If you want to supply a review topic:
git review -t topic/awesome-feature
If you want to skip the automatic "git rebase -i" step:
git review -R
If you want to download change 781 from gerrit to review it:
git review -d 781
Contributing
To get the latest code or for information about contributing, visit the project homepage at: