| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It's more convenient to have the "..." here because all of the
code-review commands use `get_merge_base`. Otherwise I'd end up having
to add it to most of the other commands.
But now, instead of only adding it to the default merge base, add it to
all merge bases, including the one set by `code-review-start`. This
makes all merge bases consistent, and means you don't have to include
the dots when setting a custom merge base.
|
|
Doesn't cover all the cases, but I think this should give us the correct
set of files when the merge base has been set via `code-review-start`.
Otherwise we might end up with a bunch of files that came from other
branches, not the one we're reviewing now.
|
|
|
|
* Use the common merge base from `code-review-database`.
* Print an absolute path to the file using `$GIT_ROOT` from
`code-review-database`. This allows the paths to be useful even when
PWD is a subdirectory in the Git repo.
|
|
Make the script a `code-review` subcommand. I had originally written it
before the `code-review-` subcommand prefix system.
|
