It's my pleasure to announce the release of git-review 2.4.0. These
are the corresponding release notes since the previous release:
New Features
------------
* By default, git rebase --abort is run automatically following a
failed test rebase, letting the user rebase again on their own if
that's the state they want to be in. A -K/--keep-rebase option is
added to get the old behavior.
* For convenience, --wip is now synonymous with the longer
--work-in-progress option.
* If HEAD already exists on a remote branch, git review will now
only warn and prompt for confirmation when pushing, in order to
let the Gerrit server decide whether to accept or reject it.
* A copy of the Gerrit upstream project's commit-msg hook is now
included directly and written to disk by default rather than
pulling a remote copy. This approach is safer and more robust, but
may break workflows for sites which rely on users retrieving a
customized commit-msg hook. For this reason, a command-line
override is provided so that users can, for example, execute git
review -s --remote-hook to get the old behavior when setting up a
new clone.
* The GIT_SSH environment variable will now be consulted, if set, in
order to determine which ssh executable to call outside of git
invocations, for consistency.
* A new --hashtags option allows specifying a list of one or more
Gerrit hashtag strings, separated by commas. Note that spaces are
not allowed either within a hashtag or between separators.
* New --message option can be used to include a custom patchset
message when pushing.
As always, the latest version of git-review is available from PyPI:
https://pypi.org/project/git-review
Current documentation can be found here:
https://docs.opendev.org/opendev/git-review
Its source code can be obtained from the OpenDev Collaboratory:
https://opendev.org/opendev/git-review
Please don't hesitate to follow up through the
service-discuss(a)lists.opendev.org mailing list or in the #opendev
channel on the OFTC IRC network if you have any questions.
--
Jeremy Stanley