Skip to content

fix(autofix): Validate Seer-supported SCM providers for Seer project preferences#112518

Merged
srest2021 merged 2 commits intomasterfrom
srest2021/validate-seer-repo-provider
Apr 8, 2026
Merged

fix(autofix): Validate Seer-supported SCM providers for Seer project preferences#112518
srest2021 merged 2 commits intomasterfrom
srest2021/validate-seer-repo-provider

Conversation

@srest2021
Copy link
Copy Markdown
Member

@srest2021 srest2021 commented Apr 8, 2026

Validate that only Seer-supported SCM providers (GitHub, GitHub Enterprise) can be added to Seer project preferences.

  • RepositorySerializer.validate_provider — rejects unsupported providers at the API layer (covers ProjectSeerPreferencesEndpoint.post and OrganizationAutofixAutomationSettingsEndpoint.post)
  • get_autofix_repos_from_project_code_mappings — filters out unsupported providers from code-mapping-derived repos (covers _resolve_project_preference and configure_seer_for_existing_org)

This covers more of Seer's deletion task cleanup_stale_seer_preferences_task, as part of the migration of Seer settings from Seer to Sentry (spec).

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 8, 2026
@srest2021 srest2021 marked this pull request as ready for review April 8, 2026 20:54
@srest2021 srest2021 requested a review from a team as a code owner April 8, 2026 20:54
@srest2021 srest2021 requested a review from a team April 8, 2026 20:58
@srest2021 srest2021 merged commit a2ff6e9 into master Apr 8, 2026
61 checks passed
@srest2021 srest2021 deleted the srest2021/validate-seer-repo-provider branch April 8, 2026 21:26
george-sentry pushed a commit that referenced this pull request Apr 9, 2026
…preferences (#112518)

Validate that only Seer-supported SCM providers (GitHub, GitHub
Enterprise) can be added to Seer project preferences.
- RepositorySerializer.validate_provider — rejects unsupported providers
at the API layer (covers ProjectSeerPreferencesEndpoint.post and
OrganizationAutofixAutomationSettingsEndpoint.post)
- get_autofix_repos_from_project_code_mappings — filters out unsupported
providers from code-mapping-derived repos (covers
_resolve_project_preference and configure_seer_for_existing_org)

This covers more of Seer's deletion task
`cleanup_stale_seer_preferences_task`, as part of the migration of Seer
settings from Seer to Sentry
([spec](https://www.notion.so/sentry/Tech-Spec-Migrate-Seer-Settings-to-Sentry-Database-3208b10e4b5d80f58ea0d7b77a301e2a)).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants