Friday, April 19, 2024
HomeProductsProductivity ToolsReviewing Code from Multiple Repositories in One Review

Reviewing Code from Multiple Repositories in One Review

Summary: This article describes new Review Assistant features, namely: the possibility to work with several repositories within a single review, and also the possibility to add nested repositories into a project.

This is the third article in the series. Learn about the improvements in Review Assistant 2.0 from the previous articles:

1. Code Review Board Re-designed

2. Improved Code Review Comments

While working on a large scale projects it is not uncommon that the source code is stored in more than one repositories. Devart’s own projects are not an exception.

From the very first release of Review Assistant there was the possibility to associate several repositories with a single project. However, while creating a new review there was only the possibility to add files from one repository.

When one repository per review is not enough

In most cases code changes to be reviewed are located in a single repository. However, there are cases when several products have shared code stored in a separate repository. In such cases a new feature may require changes in two repositories. Then, the code review should contain code from two repositories: the shared repository, the specific product repository.

Upon that, it is logical to combine changes stored in separate repositories in a single review. Previously, developers have had to create two separate reviews and make reference between them in comments.

Devart’s developers use Review Assistant in their work, and they suffered this inconvenience: they couldn’t add code from several repositories to a single review. That’s why they had been looking forward until the new feature appears. And now in Review Assistant 2.0 you have the possibility to use this feature as well.

Two Repositories in a Single Review
Two Repositories in a Single Review

It was one of the Review Assistant 2.0 features that required UI changes.

Externals, submodules, and subrepositories

Some of our users were faced with other difficulties related to repositories location structure. The core of a problem is that a repository containing common code is nested to the main project’s repository as a sub-folder.
Depending on a version control system such functionality is termed variously:

Previous version of Review Assistant didn’t allow users to add second repository to a project in case it was a nested sub-folder of the main repository. In Review Assistant 2.0 we have eliminated this restriction.

Start reviewing code

Download our peer code review tool and start reviewing code with Review Assistant for free today.

Andrey Langovoy
Andrey Langovoy
Product manager at Devart