git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Code review tool recommendations - replacement for crucible?

From
RIRichard Ipsum <richard.ipsum@codethink.co.uk>
Date
Jun 16, 2016, 10:55 UTC
Message-ID
<20160616105556.GA8721@salo>
In-Reply-To
<20160616094108.GA14661@inner.h.apk.li>
On Thu, Jun 16, 2016 at 11:41:08AM +0200, Andreas Krey wrote:
Show 19 quoted lines
> Hi all,
> 
> I'm looking for pointers to review tools that work with git (obviously),
> and can deal sensibly with bigger reviews. Things we need:
> 
> - Ability to split (set of) commits into multiple reviews,
>   so parts of changes can be reviewed by the respective owners
>   (or assign different reviewers to different files/subtrees
>   in a review).
> 
> - Tracking of files (or changes) already reviewed (due to the large numbers),
>   and of the handling of issues found so far.
> 
> - Support incremental reviews, not just e.g. over the content of a
>   pull request (bitbucket) When review comments are processed people
>   want to be able to only review that change, and not to be forced
>   to find that change in the entire previous changeset without
>   the tool's support.
> 
Hey,

Have you considered Gerrit[1] already? It would seem to handle the cases you're interested in.

[1]: https://gerrit-review.googlesource.com/Documentation/
Previous: Andreas KreyNext: Andreas Krey
Message 2 of 3 in “Code review tool recommendations - replacement for crucible?”
  1. Andreas KreyJun 16, 2016
  2. Richard IpsumJun 16, 2016
  3. Andreas KreyJun 16, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.