Skip to content

Conversation

@ryan953
Copy link
Member

@ryan953 ryan953 commented Dec 12, 2025

Followup to #104908
Depends on #104918

Currently the backend expects that all fields will be passed to the bulk-edit endpoint, but that's only true in the wizard context, when we're creating everything for the first time: https://github.com/getsentry/sentry/blob/master/src/sentry/integrations/api/endpoints/organization_repository_settings.py#L16-L41

On the settings page people can bulk-update fields, one field at a time.

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 12, 2025
@ryan953 ryan953 requested a review from a team December 12, 2025 23:52
Comment on lines +17 to 27
repositoryIds: string[];
enabledCodeReview?: never;
}
| {
codeReviewTriggers: string[];
enabledCodeReview: boolean;
repositoryIds: string[];
};

export function useBulkUpdateRepositorySettings(
options?: Omit<

This comment was marked as outdated.

srest2021 added a commit that referenced this pull request Dec 15, 2025
followup: #104912

Previously we were requiring both `enabledCodeReview` and
`codeReviewTriggers` when bulk updating. Here we allow either or both,
and don't override if a field isn't present.
@srest2021
Copy link
Member

srest2021 commented Dec 15, 2025

@sentry review
Now that the backend PR has been merged
Edit: Oh it's not been merged with master yet rip

Copy link
Contributor

@ajay-sentry ajay-sentry left a comment

Choose a reason for hiding this comment

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

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants