Skip to content

Conversation

@michelletran-sentry
Copy link
Contributor

@michelletran-sentry michelletran-sentry commented Jan 26, 2026

This feature flag looks to have been GA'ed. I'm going to attempt to remove the feature flag and clean up the code.

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 Jan 26, 2026
Remove the staff.ga-rollout feature flag and related code now that the
staff permissions system has been fully rolled out. This includes:

- Remove staff.ga-rollout and staff.user-email-allowlist options
- Remove has_staff_option() helper function
- Simplify has_elevated_mode() to always use staff permissions
- Update SuperuserOrStaffFeatureFlaggedPermission to always use staff
- Simplify permission checks across relocation and user endpoints
- Remove conditional logic that checked the feature flag

All code now assumes staff permissions are enabled, eliminating the
technical debt from the gradual rollout process.
Since we've migrated staff.ga-rollout and removed the flag, this means that
the staff user should take the place of the old superuser flag.
Updating the tests to reflect this. There were a lot of superuser uses still left in the code.
This permission is no longer relevant, and we should just use the StaffPermission.
Remove all uses of this.
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