Today’s release of RBTools 1.0.3 is a big one, featuring enhancements for Mercurial support, a vastly improved commit editing experience when landing changes, and several compatibility fixes for Python 3 and various types of repositories.
Landing Commits on Mercurial
rbt land now supports landing commits on Mercurial repositories.
You can land a local change from a Mercurial branch or bookmark, or a remote change from a review request. This will first verify that the change has been approved on Review Board before allowing it to land. Once approved, a new merge commit containing the information and URL of the review request will be placed on your destination branch.
This can also close the branch/bookmark being merged in on your behalf. See the documentation for details.
Improved Commit Editing
Patching a commit with rbt patch -c, or landing a commit with rbt land -e has always let you edit the message for the commit, but the experience was sub-par.
Now RBTools will mimic Git or Mercurial’s standard editing environment, helping your editor show the syntax highlighting or line length limits it would normally show.
Deleting all text in the editor and saving will cancel the patch/land operation.
You can also set a custom editor when working with RBTools by setting the new $RBTOOLS_EDITOR environment variable.
We’ve fixed a number of Python 3 compatibility issues. These largely centered around:
- Changes in Python 3.8
- Windows environment differences
- Editing or processing commits containing non-ASCII characters
- Normalizing URLs and paths for Subversion
- Loading in Perforce metadata
--help as the last argument
There’s also a fix for looking up available Git remotes for a branch when a tracking branch isn’t set. Thanks to Joshua Olson for this fix!
See the release notes for the full list of changes.