chore(code-review): Remove legacy code review setting toggle#111055
Merged
ajay-sentry merged 2 commits intomasterfrom Mar 19, 2026
Merged
chore(code-review): Remove legacy code review setting toggle#111055ajay-sentry merged 2 commits intomasterfrom
ajay-sentry merged 2 commits intomasterfrom
Conversation
github-actions
Bot
added
the
Scope: Frontend
TkDodo
approved these changes
Mar 19, 2026
suejungshin
approved these changes
Mar 19, 2026
This was referenced Mar 19, 2026
ajay-sentry
added a commit
to getsentry/sentry-docs
that referenced
this pull request
Mar 19, 2026
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## PR Description Needed for getsentry/sentry#111055. No longer have that organization setting, everything will be driven by the settings UI and seat based billing add-on. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [X] None: Not urgent, can wait up to 1 week+ **Before** <img width="1277" height="422" alt="Screenshot 2026-03-19 at 1 51 49 PM" src="https://github.com/user-attachments/assets/e348fcda-05c8-49f4-9aff-bd56e33bbfb1" /> **From Preview Deploy** <img width="1255" height="403" alt="Screenshot 2026-03-19 at 1 53 46 PM" src="https://github.com/user-attachments/assets/defcf72f-35f6-4aa7-a5bd-666400818d21" /> ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [X] Checked Vercel preview for correctness, including links - [X] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
ajay-sentry
added a commit
that referenced
this pull request
Mar 19, 2026
…111049) This PR does a couple things: - Simplifies code review preflight to use RepositorySettings as the source of truth across all eligible cohorts - Removes backend exposure and handling of the deprecated org option `sentry:enable_pr_review_test_generation` - Updates related tests. Higher level task: https://linear.app/getsentry/issue/CW-1005/consolidate-seer-settings-product-experience-across-legacy-and-new Depends on #111055 (removing FE toggle) Depends on https://github.com/getsentry/getsentry/pull/19606 (backfill repo settings rows) Closes https://linear.app/getsentry/issue/CW-1059/change-pointer-for-beta-orgs-to-look-at-repository-settings-rows Relates to https://linear.app/getsentry/issue/CW-1060/remove-sentryenable-pr-review-test-generation-option-values-from-db <!-- Sentry employees and contractors can delete or ignore the following. --> ### Legal Boilerplate Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
constantinius
pushed a commit
to getsentry/sentry-docs
that referenced
this pull request
Mar 20, 2026
<!-- Use this checklist to make sure your PR is ready for merge. You may delete any sections you don't need. --> ## PR Description Needed for getsentry/sentry#111055. No longer have that organization setting, everything will be driven by the settings UI and seat based billing add-on. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [X] None: Not urgent, can wait up to 1 week+ **Before** <img width="1277" height="422" alt="Screenshot 2026-03-19 at 1 51 49 PM" src="https://github.com/user-attachments/assets/e348fcda-05c8-49f4-9aff-bd56e33bbfb1" /> **From Preview Deploy** <img width="1255" height="403" alt="Screenshot 2026-03-19 at 1 53 46 PM" src="https://github.com/user-attachments/assets/defcf72f-35f6-4aa7-a5bd-666400818d21" /> ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [X] Checked Vercel preview for correctness, including links - [X] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) --------- Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Part of https://linear.app/getsentry/issue/CW-1060/remove-sentryenable-pr-review-test-generation-option-values-from-db
Closes https://linear.app/getsentry/issue/CW-1063/remove-enable-ai-code-review-toggle-fe
Blocks #111049
In the PR linked above we're swapping over to using the repository settings as the source of truth for all users: seat based, beta, or legacy. We no longer need this setting, and will remove that "legacyseer" conditional to just route to the new settings page very soon too.
Before
After
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.