With GitLab, reviews are baked into every part of the development process - so that teams can collaborate together to improve the overall quality of code and implement controls to ensure requirements are adequately implemented in the code.
Code is better with collaboration
Every code review starts with a merge request. The merge request allows team members, reviewers and approvers to collaborate with each other.
shows the changes alongside the original code - helping reviewers identify changes with ease.
Comments allow reviewers to ask clarifying questions or discuss the changes with the author and other reviewers.
Reviewers can insert
for one or more lines of code, rather than going back and forth through comments.
Code controls for better quality
To ensure only high quality code is merged into the main branch, the merge request is also the central place to implement controls
To identify the right reviewers / approvers,
can be defined for every file within the code and owners become an eligible approver for the file.
rules help define how many approvals a merge request must receive before it can be merged.
can be set up for a change. For example., for a critical backend change, without approvals from backend, database and security, the code cannot be merged.
Speed without compromising quality
Working in parallel implies many developers are making changes to the code rapidly, at the same time leading to potential conflicts.
To minimize conflicts,
pipelines for merged results
enables running the pipeline against the latest target branch without rebasing the code, as opposed to the source commit branch which could include many changes behind the target branch.
To speed up execution, pipelines from multiple merge requests can be run in parallel and be added to a
to minimize time in queuing or retrying. If there is a failure, the erring merge request is removed and all subsequent pipelines are restarted without manual intervention.
Continuous improvement through insights
Interpreting data to derive insights for improvement is what gives teams an edge over others.
Code quality reports
help developers identify code quality changes directly in the merge request. Quality violations are also shown on the merge request diff view to enable developers to resolve the violations before the code is merged to maintain the overall health of the code quality.
Code review analytics
helps to analyze patterns and trends related to code reviews that could be slowing down the development cycle time.