Support for monorepos

[JJ]

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.)?

[prashant]

+1 there needs to be more documentation on how monorepos work with compass

[Ivan Diana]

+1 needs to understand how it could be work with monorepo

[Tyler T]

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 or API, 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.

[Joshua Chaitin-Pollak]

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

[Michelle Carr]

+1 having same issue here