GitLab Duo reviews within the GitLab workflow
The current Code Review Flow uses repository structure and cross-file dependencies to review merge requests. It supports custom instructions and automated review within the GitLab Duo Agent Platform.
GitLab documents this agentic flow separately from its earlier non-agentic review feature. Use the documentation and configuration for the version you intend to run.
GitLab Duo and Proofline side by side
Documented workflows and the evidence to inspect. Custom tools and configuration can change what a review can access.
Scroll the table horizontally to compare both products.
| Compare | GitLab Duo | Proofline |
|---|---|---|
| Source host | GitLab merge requests, within the supported GitLab Duo setup. | GitHub repositories. Proofline is not a drop-in GitLab merge request reviewer. |
| Review context | Repository structure, cross-file dependencies, and custom review instructions. | Pinned code input and recorded infrastructure facts for the selected environment. |
| Adoption question | Which Duo features and execution configuration are available in your GitLab installation? | Is your repository supported, and do the configured connectors cover the deployment question? |
How Proofline investigates changes explains its code and environment inputs. Check connector coverage before assuming that an assessment can observe a resource.
A pipeline changes which image reaches the environment
Suppose a pipeline edit changes an image reference from an immutable digest to a mutable tag. The application code remains unchanged.
The release question is which image the pipeline actually deploys and how that identity relates to the reviewed source. A useful investigation follows the build output and deployment configuration instead of assuming that the branch name identifies the running artifact.
This illustrative case can guide a GitLab Duo evaluation. It is not a claim that Proofline integrates with GitLab CI. If your repositories live only in GitLab, start by establishing a supported evaluation path rather than assuming equivalent onboarding.
Source-host support comes first
Choose GitLab Duo when you need review inside your existing GitLab merge request workflow. For a GitHub repository, evaluate Proofline when a release question depends on recorded infrastructure configuration.
If GitLab support is a requirement, discuss your setup with Proofline before planning an adoption. A comparison page does not establish an integration or a delivery commitment.
Questions about GitLab Duo and Proofline
Can Proofline replace GitLab Duo in my merge requests today?
Proofline currently supports GitHub repositories. It does not offer equivalent GitLab merge request onboarding.
Does Duo only inspect the changed lines?
No. The documented Code Review Flow uses repository and cross-file context. Inspect its configured environment and instructions when evaluating what information it can use.
Try a change from your own repository
Connect a GitHub repository and its deployment environment, then inspect the evidence behind the findings. Missing evidence stays visible; a review without findings does not establish deployment success.
View pricing and availability or discuss your setup with us.
Get Started with GitHub