We have a plan and partial implementation for repository-spanned changes.
We’re considering it for Review Board 5.
Christian
On Thu, Aug 6, 2020 at 04:21 Paul Mansfield
wrote:
>
> how about having reviews follow the epic/story model... a parent review
> with child reviews. Each child review
how about having reviews follow the epic/story model... a parent review
with child reviews. Each child review would be associated with individual
repositories, and you then set it so that nothing can be landed until all
related reviews are marked as ship-its?
this might be much easier to achieve
+1 for this feature because we would also need this.
My organization is planning to transition from a huge SVN instance to ~100
small Git repo-s.
The biggest hurdle we see is that many of our developments will affect
multiple repositories so we need a code-review tool that can work on
Hi Radek,
This is really a lot more work than it seems like it'll be.
Diff files themselves have no concept of a repository they're associated
with. We do have a repository reference for DiffSet model entries, but
you're not going to squeeze multiple concurrent DiffSets onto a review
request.
Hi all,
I'm also interested in this feature since the group I'm working with uses
git submodules and we are interested in a coherent review. But since there
was no interest from review board developers so far I wanted to ask: where
should I start to implement a proof of concept for git? I'm
Hi,
I just jump into this conversation to say that we have the same problem
here: we have to manage a "review" as a set of changes across multiple
repositories.
So +1 for this feature to be implemented.
Thanks,
Eric
--
Supercharge your Review Board with Power Pack:
Joseph,
There's no way for a single review request to span repositories. What you
can do (and what we recommend) is to use the "depends on" field to indicate
the interdependencies between the changes in each repository.
Making custom rbt commands is pretty easy. You can either do it in Python,
Hello,
Me and my team have been successfully using ReviewBoard for about half a
year now, and I am looking at rolling it out to the whole of R
The only problem that we have so far, is that many times, our code changes
are across multiple repos. I have been able to work around this with CVS by
