Skip to content

fix(seer): Remove code mappings fallback from has_project_connected_repos#113509

Merged
srest2021 merged 2 commits intomasterfrom
srest2021/connected-repos-code-mappings
Apr 21, 2026
Merged

fix(seer): Remove code mappings fallback from has_project_connected_repos#113509
srest2021 merged 2 commits intomasterfrom
srest2021/connected-repos-code-mappings

Conversation

@srest2021
Copy link
Copy Markdown
Member

@srest2021 srest2021 commented Apr 21, 2026

has_project_connected_repos now checks only Seer project preferences to determine whether a project has connected repos.

Consistent with #113077 (don't fall back to code mappings if it's our first autofix run) and #113369 (bill based on connected project repositories, instead of code mappings).

`has_project_connected_repos` now checks only Seer project preferences
to determine whether a project has connected repos. The prior fallback
to `get_autofix_repos_from_project_code_mappings` is removed — a
project without prefs-configured repos is treated as unconnected.
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 21, 2026
…d_repos

Remove tests covering the code-mapping fallback path and simplify the
remaining tests to no longer mock `get_autofix_repos_from_project_code_mappings`.
@srest2021 srest2021 changed the title fix(seer): Drop code-mapping fallback from has_project_connected_repos fix(seer): Remove code mappings fallback from has_project_connected_repos Apr 21, 2026
@srest2021 srest2021 marked this pull request as ready for review April 21, 2026 16:41
@srest2021 srest2021 requested a review from a team as a code owner April 21, 2026 16:42
@srest2021 srest2021 merged commit 684ca45 into master Apr 21, 2026
63 checks passed
@srest2021 srest2021 deleted the srest2021/connected-repos-code-mappings branch April 21, 2026 17:17
srest2021 added a commit that referenced this pull request Apr 21, 2026
…isting org (#113582)

Fixes CW-1182

Since we will bill by connected repos
#113369, let's remove the code
mappings fallback when configuring Seer for an existing org and there
are no existing repos in the project preference. Ultimately we want to
avoid bill shock by adding stuff to users' preferences that will get
billed.

Consistent with #113077 and
#113509.

[More
context.](https://sentry.slack.com/archives/C0AAF0JD0GK/p1776284922120519)
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