How to Map Sources to Repositories Private Beta

The Sources tab connects each of your RudderStack sources to the GitHub or GitLab repository where that source’s events are instrumented. This mapping lets Lookout connect your data to the code that produces it, so when you ask for a tracking change, it knows exactly which repository needs a pull request.

Prerequisites

Mapping a source to a repository connects two systems, so both must already be set up:

• RudderStack integration set up, so your sources are available to map
• A linked GitHub or GitLab repository

Map a source to a repository

From Settings > Sources, select Connect Source, then configure these settings:

The Sources tab lists your sources with their current mappings and shows any sources that aren’t connected yet, so you can map them.

How it works

Your events are defined in your warehouse and tracking plans, but they are emitted by analytics calls in your application code — this code lives in a repository. The Sources tab records which repository (and, for monorepos, which subfolder) corresponds to each source.

With the source-repository mapping in place, a request like “Start capturing a checkout_started event so it reaches our warehouse” becomes actionable end to end:

1. Lookout identifies the source the event belongs to
2. It looks up the repository mapped to that source
3. It proposes the instrumentation change as a pull request against the right repository — and the right subfolder

This mechanism powers Measurement Plans and the instrumentation agent. Without the mapping, Lookout would know what to change but not where.