Problem Statement
Teams need a way to surface newly captured Sentry errors directly within relevant pull requests to improve visibility during testing and review. Today, PR comments are limited to existing unresolved issues on open PRs or retrospective suspect commit comments on merged PRs, and draft PRs are not supported. This makes it difficult to proactively alert developers when new errors are introduced during manual or sandbox testing, especially when Slack notifications are missed or noisy. Enabling configurable, event-driven comments on active (open/draft) PRs would provide more targeted, actionable feedback during the development lifecycle.
Solution Brainstorm
No response
Product Area
Unknown
Problem Statement
Teams need a way to surface newly captured Sentry errors directly within relevant pull requests to improve visibility during testing and review. Today, PR comments are limited to existing unresolved issues on open PRs or retrospective suspect commit comments on merged PRs, and draft PRs are not supported. This makes it difficult to proactively alert developers when new errors are introduced during manual or sandbox testing, especially when Slack notifications are missed or noisy. Enabling configurable, event-driven comments on active (open/draft) PRs would provide more targeted, actionable feedback during the development lifecycle.
Solution Brainstorm
No response
Product Area
Unknown