Support for monorepos

Question

Adding a repository to a component worked well but if that repository is a monorepo with multiple components it's not possible to filter out the different metrics based on different rules.

Is there a different option that can be configured (eg. grouping PRs with a certain label inside a monorepo, filtering releases etc.)?

John Homenuke · Answer

I tried nesting `isMonorepoProject` under `fields` and I got this error response:

Tyler T · Answer

While full monorepo support is not yet available, Compass now allows you to stop SCM powered metrics from monorepo components. Currently this is supported via the UI,  API, and config-as-code not config-as-code -> https://developer.atlassian.com/cloud/compass/config-as-code/manage-components-with-config-as-code/#managing-multiple-components-with-config-as-code-in-a-single-repository

On the component overview page, select more actions (•••) then Component of a monorepo and enable this setting. This will prevent capturing activity (events, metrics) across the entire monorepo with the Bitbucket, GitHub, and GitLab integrations. In the future we'll add a property to manage this setting via configuration as code. Send events and metrics for this component using our API.

March 2025 UPDATE

This is now supported in Config-as-Code:

fields:

isMonorepoProject: true

Joshua Chaitin-Pollak · Answer

I'm on day-zero with Compass having just enabled it a few minutes ago, but does this section of the documentation help?

https://developer.atlassian.com/cloud/compass/config-as-code/manage-components-with-config-as-code/#managing-multiple-components-with-config-as-code-in-a-single-repository