Within a commit view or a merge request diff view, and with respect to a specific location of an image, you can have a resolvable discussion. Have multiple discussions specifying different areas of an image.
Merge Request Commit Discussions
Comment on a commit within the context of a merge request itself
Multiple approvals in code review
In GitLab, to ensure strict code review, you can require a specific number of approvals on a merge request by different users before being able to merge it. You can undo an approval by removing it after the fact.
Approval rules for code review
Make sure the right people review merge requests with approval rules by specifying lists of eligible approvers and minimum number of approvals for each. This makes it easy to request review from different teams like Engineering, UX and Product.
When a project requires multiple sign-offs, GitLab Enterprise Edition enables you to make sure every merge request is approved by one or more people. Merge request approvals allow you to set the number of necessary approvals and predefine a list of approvers that will need to approve every merge request in a project, and in-turn improve your code’s quality.
Inline commenting and discussion resolution
Code or text review is faster and more effective with inline comments in merge requests. Leave comments and resolve discussions on specific lines of code. In GitLab, Merge Request inline comments are interpreted as a discussion and can be left on any line, changed or unchanged. You can configure your project to only accept merge requests when all discussions are resolved.
Assign Code Owners to files to indicate the team members responsible for code in your project using a `CODEOWNERS` file. Code owners are assigned automatically as merge request approvers, can be set as required and shown when viewing files.
Code review dashboards
Dashboards with a filterable set of code reviews (could be by project, by user, by branch, by status, or a combination of those). Dashboards includes code review status and links to get to them. This makes it easy to see what is going on with code reviews for a desired subset.
Users can be required to sign one or more contributor agreements before being able to submit a change in a project.
Support for inline comments that are generated by automated third-party systems, for example robot comments can be used to represent the results of code analyzers.
Works with multiple repository types
Supports more than one repository type, such as Git, Subversion, Perforce, CVS, Mercurial.