How Lookout Manages PR and MR Reviews Private Beta

Lookout can automatically review incoming pull requests (GitHub) and merge requests (GitLab) for changes that would break your data contract — so a problem is caught in code review rather than discovered later in the warehouse.

How it works

When a pull or merge request is opened or updated in a connected repository, a review agent inspects the diff for changes that would break the data contract, like:

• Renamed or removed events
• Altered property types
• Dropped fields

It posts its findings back as review comments on the pull or merge request, right where your team is already reviewing the change.

Why it helps

Instrumentation drift is usually invisible until the data is already wrong — a renamed event or a dropped property quietly breaks a dashboard or a downstream sync days later. Reviewing the diff at code-review time moves that catch to the earliest possible point, where the change is still easy to fix.

Setup requirements

An automated review depends on three requirements being in place:

• A connected repository: Install the GitHub App so Lookout receives pull-request events, or connect your GitLab instance so it receives merge-request events. See GitHub and GitLab for details.
• A source-to-repository mapping: The repository must be mapped to the RudderStack source it instruments, so Lookout knows which data contract to check. See Sources for more information.
• Auto PR review enabled: The per-source Auto PR review toggle (under Settings > Sources) must be on. An admin can turn it off for a source to stop reviews.

When these requirements are in place, review happens automatically on incoming pull and merge requests — no per-request action is needed.