Token Controller Docs
Docs / Attribute / Repository mapping

Repository mapping

Mapping a repository to a project places every session in that repository on the project, when no ticket matches.

Browse the docs

Map a repository

In the web app, open the project and add its repositories, such as kestrel/storefront. One repository belongs to one project.

What gets placed

Sessions in a mapped repository with no ticket key land on the project as project overhead. Sessions outside any mapped repository and without a ticket key stay unattributed.

Repository mapping is the only placing that works with telemetry alone, because telemetry sees the repository but not the branch.

Last updated 8 October 2026 · Edit this page © 2026 Jan Beck · Privacy · Imprint