Submitting review efcba5b

Better support for rebasing reviews

This change improves the support for rebasing reviews in multiple ways:

1. Adding a new `refs/archives/devtools` ref that can be used to make sure that commits which have been rebased do not get garbage collected.
2. Adding a new `alias` field to the request schema that enables tracking review history across rebases.
3. Adding a new `rebase` subcommand that enables us to update the history for a change prior to submitting it.

Submitting review ea1f988

Add more integrations to the README

Submitting review dfdd159

Consolidate the editor logic into a single place, and make it more reliable.

With this change we will try to run the editor in a shell if launching it directly does not work.

Submitting review 8db99d4

Split out the summary of a review into a separate struct.

This new struct is then returned by all of the methods that list the
reviews in a repo, and is what the "list" subcommand operates on.

By making this split, we can separate the data that is cheap to look up
from the data that is expensive to look up, and forgoe the expensive
look ups when we are operating on multiple reviews.

This change improves the performance of listing the open reviews in the
git-appraise repo by more than three fold (dropping the run time from
more than 7 seconds to less than 2).

The second version of the tool, which provides a minimal but function…

…ally complete (and consistent) CLI for code review

The initial version of the tool, which only allowed commenting upon t…

…he current review