feat(seer): Add is_private field to repo definitions for code review#110190
Merged
feat(seer): Add is_private field to repo definitions for code review#110190
Conversation
Populate is_private from the GitHub webhook payload's repository.private field when building repo definitions for Seer code review requests. The field is set in _build_repo_definition, which receives the event payload through _common_codegen_request_payload. Also adds the optional is_private field to SeerRepoDefinition and SeerCodeReviewRepoDefinition models (defaults to None). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Include repo privacy status in the tags emitted for code review webhook events, matching the scm_repo_is_private tag added on the Seer side in getsentry/seer#5165. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
joseph-sentry
approved these changes
Mar 9, 2026
Contributor
joseph-sentry
left a comment
There was a problem hiding this comment.
not sure if we need to add it to SeerRepoDefinition since it doesn't seem to be consumed anywhere but i don't see a reason not to either
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add
is_private: bool | None = NonetoSeerRepoDefinitionandSeerCodeReviewRepoDefinitionmodels, and populate it from the GitHub webhook payload'srepository.privatefield when building code review requests for Seer.The field is extracted in
_build_repo_definitionwhich now receives the webhookevent_payloadthrough_common_codegen_request_payload. This avoids any extra GitHub API calls — the data is already present in everypull_requestandissue_commentwebhook.For non-webhook flows (autofix, coding agents), the field defaults to
Nonesince the webhook payload isn't available in those contexts.Seer PR https://github.com/getsentry/seer/pull/5165
Implements CW-986