Code reviews are a way for you to collaborate on your project through peer assessment. Once you complete work on a changeset or branch, you can request a code review from someone to check over or contribute to the changes. Code reviews can improve your code quality as they help you catch bugs, share knowledge, and enhance control.

For information on how to use code reviews, refer to Navigate code reviews.

A code review contains Conversations, which you can use to interact with collaborators. You can either add comments and replies in the Conversation tab, or you can add questions and request changes to a specific section of code in the Changed files tab. Each comment you add to the code appears in the Conversations panel.

A code review also contains a list of the changed files that are submitted for review.

This tab allows you to filter and navigate through the changed files, and add comments. You can also filter through any existing comments on the files, and view the status and type of comment.

These comments can either be a Question or Change request, and display as either Resolved or Unresolved.

A reviewer can change the status of the Code review to one of the following statuses:

If you leave a Change request comment unresolved, an unresolved button displays that directs you to the unresolved comments.

By default, you can’t merge the code review until a reviewer marks the review as Reviewed. For more information, refer to merge rules.