We use a separate Sentry project for testing Sentry integration in local development environments so that local-only issues don't pollute the project that tracks issues in deployed environments. When someone has a misconfiguration or such in their local env that results in a Sentry issue, Sentry's GitHub integration sometimes adds a comment to the PR that might've caused the issue:
While this feature is generally useful, it becomes a noise when it's from the project for local testing, taking up people's time investigating what turns out to be a non-issue.
Solution Brainstorm
Allow configuring these features project by project:
Problem Statement
We use a separate Sentry project for testing Sentry integration in local development environments so that local-only issues don't pollute the project that tracks issues in deployed environments. When someone has a misconfiguration or such in their local env that results in a Sentry issue, Sentry's GitHub integration sometimes adds a comment to the PR that might've caused the issue:
While this feature is generally useful, it becomes a noise when it's from the project for local testing, taking up people's time investigating what turns out to be a non-issue.
Solution Brainstorm
Allow configuring these features project by project:
Product Area
Settings - Integrations