Issue
We have one CODEOWNERS file at the root of our monorepo. Each deployable target has a separate project in Sentry. When linking the CODEOWNERS file to a project, it seems like we have to add all teams to every project to get rid of the warnings/errors. This is probably because we have 1 shared codeowner file which mentions all of the teams, even when they are not involved in a project (not in the app code, not in the shared code).
Is there a better way of handling monorepos in Sentry?
Applies To
- Business or Enterprise SaaS Customers
- Issue Ownership
- Integrations
Resolution
Unfortunately there is no better way to go about this, unless you manually set your own ownership rules, but that would beat the purpose of using CODEOWNERS.
However, you can at least prevent notifications from being sent to teams that are not actually involved in a project. It just requires every user to configure this setting manually.
They can go to their User settings > Notifications > Issue Alerts. There, they can configure the settings of an Organization they are a member of by choosing a project and setting the value to "Off" so that they don't receive alert rule notifications for that project.
Similarly, they can make the same configuration in any other category from User settings > Notifications if they are receiving notifications by any of these categories (Issue Workflow, Deploys, etc.).