fix(seer-prefs): repo cleanup for org deleted repos

[jennmueng]

When you delete a repo from the UI (the PUT endpoint) we'll delete it from seer preferences as well.

Tested locally with sentry <-> seer

[codecov]

Codecov Report

Attention: Patch coverage is 99.12281% with 1 line in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
tests/sentry/tasks/test_seer.py	97.50%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #95768       +/-   ##
===========================================
+ Coverage   38.57%   87.78%   +49.21%     
===========================================
  Files        9966    10577      +611     
  Lines      559498   610100    +50602     
  Branches    23972    23844      -128     
===========================================
+ Hits       215806   535560   +319754     
+ Misses     343408    74246   -269162     
- Partials      284      294       +10     

[cursor]

Bug: Seer API Provider Format Inconsistency

The cleanup_seer_repository_preferences task sends repo.provider to the Seer API. However, the repo.provider field can be inconsistently formatted: it may include an "integrations:" prefix (e.g., "integrations:github") when the repository is linked via an integration, while other cases might use just the provider name (e.g., "github"). This inconsistency can cause issues if Seer expects a uniform provider format.

src/sentry/integrations/api/endpoints/organization_repository_details.py#L100-L108

sentry/src/sentry/integrations/api/endpoints/organization_repository_details.py

Lines 100 to 108 in e69d54b

	if repo.external_id and repo.provider:
	cleanup_seer_repository_preferences.apply_async(
	kwargs={
	"organization_id": repo.organization_id,
	"repo_external_id": repo.external_id,
	"repo_provider": repo.provider,
	}
	)

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎