getsentry / getsentry/sentry

Feature Request: Have the option to disable non-actionable GitHub Commit Fetch Errors

Open
#87,266 7 comments 3 reactions 0 assignees View on GitHub
Component: Notifications Product Area: Settings - Integrations Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

Sentry currently sends email notifications whenever it fails to fetch the commit log for a release from GitHub. The error message typically looks like this:

`We were unable to fetch the commit log for your release for repository in the organization due to the following error: Error Communicating with GitHub (HTTP 500): unknown error`

The customer is requesting an option to suppress error notifications related to intermittent GitHub commit fetch failures (HTTP 500) in Sentry. These errors are not actionable on their end and are typically due to temporary issues on GitHub’s side.

Contributor guide

Open the contributing guide

Research direction

Trace the release GitHub commit-log fetch failure path and the notification handling for intermittent HTTP 500 errors. Define where an option to suppress these non-actionable notifications belongs, then add coverage showing that the option suppresses the targeted failures without hiding other errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.