Our GitLab Code Review Integration

Make Your Pull Requests Mean More with Comprehensive Peer Reviews in Collaborator

Interested in a trial? Start a Free 30 Trial


Improving Your Pull Request Workflow

Many teams kick off their code review workflow with a simple pull request, notifying teammates that their code is ready to review. While that's a good place to start, repositories are not designed with code review management in mind. Our Collaborator GitLab integration lets you:

  • Import multiple repositories with one click
  • Initiate a pull request and automatically create a code review in Collaborator
  • Generate reviews on pushes and block merges until the review is complete
  • Collaborator can be configured to automatically merge your pull request and close out its branch when a review is completed

Adding Peer Code Review Quality Gates

Create Collaborator Reviews Automatically For Each Pull Request

Pull requests in GitLab can be a quick way to collaborate. For teams that need more robust reviews, Collaborator offers more comprehensive peer reviews, with elements like custom checklists, required partipants, and detailed reports.

Our GitLab integration is based on the pull request workflow. Whenever you create a pull request, Collaborator can automatically create and link to a new review. This allows you to use the workflows you are comfortable with while adding rigor to your review process.

Complete Reviews and Merge Seamlessly

When all checklist items have been completed by reviewers, Collaborator can close out the review and merge your pull request automatically. By extending the pull request workflow, your team now has access to review metrics like defect density, time spent on reviews, lines of code reviewed, and more.

These customizable reports can be downloaded to a zip file easily, which means it is simple for your team to maintain an audit trail and meet compliance standards.

My team is currently conducting reviews with pull requests in GitLab. Why would we need Collaborator for reviews?

For some teams, conducting code review through pull requests in GitLab is enough, especially for small changes. Conducting reviews in GitLab might be convenient, it does dramatically limit your team's code review process. Through its GitLab integration, Collaborator enables teams to customize their review process with custom fields, workflows, checklists, and participant rules. Your team can also specify comments versus defects so you can capture key metrics on your process, like defect type and severity, inspection rate, and lines of code reviewed, and use the review as a quality gate. Collaborator also lets your team go beyond just reviewing code, since it also supports document review. If you want to build a review process that includes multiple artifact types and drives continuous improvement, it is easy to integrate Collaborator with GitLab and ensure quality code is being merged.

When is a review created using the GitLab integration?

A review will be created when either a pull request or push/commit is made to a branch that Collaborator is told to track.

How do I get to the review in Collaborator once one has been created by the GitLab integration?

When a review is created by a pull request or push/commit, Collaborator will leave a comment with a link to the review on the pull request or push/commit.

Can I create a review for a pull request from Collaborator?

No – the review is created when the pull request event occurs in GitLab with a destination branch monitored by Collaborator. To ensure that reviews are created for all branches that need a review prior to merge, change your branch settings for that repositories integration.

Who’s account will the Collaborator review be associated with when it is created by the GitLab integration?

Collaborator will try to associate the GitLab user that initiated the pull request / commit with a Collaborator user. If the GitLab user name matches a Collaborator user name, the review will be created under that Collaborator account. If Collaborator cannot find any users that match the GitLab user name, it will check to see if any users have mapped their Collaborator user name to the GitLab user name; if it finds a match, the review will be created under that Collaborator account. If Collaborator cannot find any Collaborator users who match the GitLab user name, or are mapped to the GitLab user name, the review will be created under the Admin user.

As I continue to develop, can I update a review with new commits after a review is created?

If a review is created by a pull request, as you merge code into your pull request, the Collaborator review will be updated.

What happens if I perform rebasing operations on the commits involved in my pull request after a review is created?

The Collaborator review will update itself to match the git history of the pull request. For example, if you squash several commits in your pull request, the Collaborator review will reflect that. We will not remove comments left on versions of a file that have been rebased out of a review.

What happens if I merge in upstream changes to my pull request after a review is created?

The Collaborator review will update accordingly, and by default, will not highlight these changes in the diff viewer.

What happens when I leave comments on a GitLab PR? How about a Collaborator review?

Comments will propagate from GitLab to Collaborator, but will NOT propagate from Collaborator to GitLab.


Start a Free Collaborator Trial Now

By submitting this form, you agree to our Terms of Use and Privacy Policy

Collaborator is the peer review tool for software teams that care about code quality and collaboration.

Here's what your 30-day trial could look like:

  • Invite other team members to join and get started reviewing source code, requirements, design docs, user stories, and more.
  • Connect with your other development tools so that code reviews are a seamless part of your process.
  • Have a question? We will be available through chat to help your team get the most out of your trial.
  • Set up custom templates, checklists, and groups to ensure that your reviews focus on what's important to your team.
  • View reports on your review process to see what types of defects your team is finding and how effective your reviews are.

Collaborator supports multiple SCMs at once: TFS, Git, Perforce, Subversion, Rational Team Concert, Synergy, ClearCase, AccuRev, CVS, and PTC Integrity.