-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
feat(seer): Update Seer settings so that PR Create toggles respect enableSeerCoding #107391
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| )} | ||
| </Flex> | ||
| ), | ||
| key: 'pr_creation', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bulk action bypasses enableSeerCoding restriction for PR Creation
Medium Severity
The PR Creation column header tooltip and individual row switches correctly check organization.enableSeerCoding === false to disable the feature, but the bulk action DropdownMenu for "PR Creation" (shown when projects are selected) only checks canWrite. Users can bypass the enableSeerCoding restriction by selecting multiple projects and using the bulk dropdown to enable PR creation, even when code generation is disabled at the org level.
Additional Locations (1)
| )} | ||
| </Alert> | ||
| )} | ||
| </Flex> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Settings toggle not disabled when code generation disabled
Medium Severity
The autoOpenPrs field shows an Alert warning when organization.enableSeerCoding === false, but unlike the project-level components (seerAgentSection.tsx and seerProjectTableRow.tsx), it doesn't disable the toggle. This allows users to enable the setting despite the warning that it won't work. The field definition supports a disabled property (as seen in the form types), but one isn't provided for this case, creating inconsistent behavior across the UI.
| ), | ||
| } | ||
| )} | ||
| </Alert> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicated warning message pattern across three files
Low Severity
The identical tct('[settings:"Enable Code Generation"] must be enabled...') message with the same Link to={...seer/#enableSeerCoding} pattern is duplicated across three files. Consider extracting this into a shared helper function or constant (e.g., getSeerCodingDisabledMessage(orgSlug)) to reduce maintenance burden.


Fixes CW-733