Skip to content

fix(seer): Remove code mappings fallback when configuring Seer for existing org#113582

Merged
srest2021 merged 3 commits intomasterfrom
srest2021/code-mappings-configure-for-existing-org
Apr 21, 2026
Merged

fix(seer): Remove code mappings fallback when configuring Seer for existing org#113582
srest2021 merged 3 commits intomasterfrom
srest2021/code-mappings-configure-for-existing-org

Conversation

@srest2021
Copy link
Copy Markdown
Member

@srest2021 srest2021 commented Apr 21, 2026

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.

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 21, 2026
@srest2021 srest2021 marked this pull request as ready for review April 21, 2026 20:27
@srest2021 srest2021 requested a review from a team as a code owner April 21, 2026 20:27
@linear-code
Copy link
Copy Markdown

linear-code Bot commented Apr 21, 2026

JoshFerge

This comment was marked as resolved.

@srest2021 srest2021 merged commit 76654a4 into master Apr 21, 2026
56 checks passed
@srest2021 srest2021 deleted the srest2021/code-mappings-configure-for-existing-org branch April 21, 2026 21:39
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