Repository navigation
ref(integrations): Remove duplicate search lifecycle - #129471
Open
giovanni-guidini wants to merge 1 commit into
Open
giovanni-guidini wants to merge 1 commit into
giovanni-guidini wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
Keep issue and repository search handlers as the authoritative SCM feature outcomes. Refs SCM-304
giovanni-guidini
force-pushed
the
gio/refactor/demote-scm-search-get
branch
from
November 3, 2026 09:18
741fc79 to
3908d5d
Compare
giovanni-guidini
marked this pull request as ready for review
November 3, 2026 10:54
joseph-sentry
approved these changes
Nov 3, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the generic
getSCM lifecycle from Sentry’s source-code search endpoint so issue and repository search handlers remain the single authoritative feature outcomes, while request validation and routing continue to use ordinary endpoint telemetry. This removes duplicate and contradictory SLO events and advances SCM-304.Made with Cursor