There has been a long-standing misconception that git-review pushes automatically rebased changes by default. It does not, but our documentation and context help have been less than clear on that point, contributing to this impression. Try to do a better job of explaining that the default rebasing performed by git-review is purely exploratory, and used only to notify users about possible merge conflicts with their target branch before pushing a change. Change-Id: I3c841af5ff9430a0de4d9dc9526dd3be6ab53ad2
1.5 KiB
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 subscribe some reviewers:
git review --reviewers a@example.com b@example.com
If you want to disable autogenerated topic:
git review -T
If you want to submit a branch for review and then remove the local branch:
git review -f
If you want to be able to push a change which has a merge conflict with the remote branch:
git review -R
If you want to download change 781 from gerrit to review it:
git review -d 781
If you want to download patchset 4 for change 781 from gerrit to review it:
git review -d 781,4
If you want to compare patchset 4 with patchset 10 of change 781 from gerrit:
git review -m 781,4-10
If you want to see a list of open reviews:
git review -l
If you just want to do the commit message and remote setup steps:
git review -s
Note
If using multiple SSH keys (identities) or SSH keys with passphrases, you may wish to use a tool like ssh-agent__, Gnome Seahorse__ or KDE KWallet__ to avoid manual SSH configuration or frequent passphrase requests.
__ https://www.ssh.com/ssh/agent __ https://wiki.gnome.org/Apps/Seahorse __ https://userbase.kde.org/KDE_Wallet_Manager