Skip to content

[fix] Fix get_organization_seer_consent_by_org_name to only obey UI toggles #96725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 30, 2025

Conversation

rohitvinnakota-codecov
Copy link
Member

The get_organization_seer_consent_by_org_name controls the consent flow for Prevent AI features via the seer-by-sentry GitHub app. We want the consent gated by 2 toggles only. The Show Generative AI Features toggle, and the Enable PR review and test generation toggle.

We were using the get_seer_org_acknowledgement function before, but that is not required for this flow.

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.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 30, 2025
@rohitvinnakota-codecov rohitvinnakota-codecov marked this pull request as ready for review July 30, 2025 13:12
@rohitvinnakota-codecov rohitvinnakota-codecov requested a review from a team as a code owner July 30, 2025 13:12
Copy link
Member

@suejung-sentry suejung-sentry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the update to get to the desired end state makes sense to me, had 1 question

@@ -229,18 +233,16 @@ def get_organization_seer_consent_by_org_name(
for org_integration in org_integrations:
try:
org = Organization.objects.get(id=org_integration.organization_id)
seer_org_acknowledgement = get_seer_org_acknowledgement(org_id=org.id)
github_extension_enabled = org.id in options.get("github-extension.enabled-orgs")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

github_extension_enabled = org.id in options.get("github-extension.enabled-orgs")

Do you know what does github-extension.enabled-org mean ? Does that mean the user in the Sentry UI somewhere consented to use of the sentry.io github app or something? If so, do we need to preserve this check?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is copilot related, so we can ignore that.

@rohitvinnakota-codecov rohitvinnakota-codecov merged commit c1b669c into master Jul 30, 2025
65 checks passed
@rohitvinnakota-codecov rohitvinnakota-codecov deleted the rvinnakota/fix-seer-org-name-consent branch July 30, 2025 16:16
andrewshie-sentry pushed a commit that referenced this pull request Aug 4, 2025
… toggles (#96725)

<!-- Describe your PR here. -->

The `get_organization_seer_consent_by_org_name` controls the consent
flow for Prevent AI features via the seer-by-sentry GitHub app. We want
the consent gated by 2 toggles only. The `Show Generative AI Features`
toggle, and the `Enable PR review and test generation` toggle.

We were using the `get_seer_org_acknowledgement` function before, but
that is not required for this flow.


<!--

  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.
@github-actions github-actions bot locked and limited conversation to collaborators Aug 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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