This page documents code review practices used for Software Heritage development.
GitLab has many useful features to ease reviewing the changes, communicating around questions or comments, and making suggestions. Learning how to use them will help you and the team.
Please adhere to the following guidelines in the context of Software Heritage development.
When submitting changes:
Reviews are strongly recommended for any non-trivial code change, but not mandatory (nor enforced at Git level).
The code submission workflow is implemented using merge requests sent to our GitLab instance.
The assignee in the context of merge request is the person supposed to drive it to completion. In almost all cases, you should assign yourself to merge requests you create.
If your changes are meant to address a specific issue, you should prefix the branch name with the issue number.
Feel free to explicitly mention one or more specific reviewer from people most knowledgeable with the target code. You can also assign a single person  as reviewer using the relevant field. It will prevent the merge request from going unnoticed.
One approval is enough before merging a request.
As a team member:
Review any merge requests you want: no matter the suggested reviewers, feel free to review any pending merge requests.
Review every day: reviews should be timely as fellow developers will wait for them. To make the process sustainable each developer should strive to dedicate a fixed minimum amount of review time every workday.
Learning about pending reviews#
As we aim to review merge requests in a timely manner, here are several ways to know about merge requests waiting for input.
To be sure to receive notifications of new merge requests:
Open the notification controls for your GitLab account.
Locate the Platform group.
Select Custom in the list of notification levels.
Click on the bell icon.
Make sure New merge request is ticked. You probably also want to select at least New issue, Failed pipeline, and Fixed pipeline.
Repeat the operation for other groups of interest.
List pending merge requests#
Sadly, notifications can easily be missed and GitLab by itself does not provide a view with all merge requests waiting for action across multiple projects. To have a better view of pending merge requests, you should consider using:
Best practices (Palantir) ← comprehensive and recommended read, especially if you’re short on time
Review checklist (Code Project)
Motivation: code quality (Coding Horror)
Motivation: team culture (Google & FullStory)
Motivation: humanizing peer reviews (Wiegers)
Motivation: sharing knowledge (Atlassian)