-
Notifications
You must be signed in to change notification settings - Fork 879
feat: unify organization and deployment management settings #13602
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
Conversation
site/src/pages/ManagementSettingsPage/CreateOrganizationPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/CreateOrganizationPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/CreateOrganizationPageView.stories.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/ManagementSettingsLayout.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/OrganizationSettingsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/OrganizationSettingsPage.tsx
Outdated
Show resolved
Hide resolved
site/src/pages/ManagementSettingsPage/OrganizationSettingsPageView.stories.tsx
Outdated
Show resolved
Hide resolved
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.
Left a few comments related to the code and about tests, since this is an important feature, I would add e2e tests to cover the critical flows:
- Create a new org
- Update a org
- Delete a org
This comment was marked as resolved.
This comment was marked as resolved.
We can adjust that, but that's a backend problem. |
It's behind an experiment, so I can't yet. 😅 |
actually I guess I can just add it to the env variable in the e2e test config |
Improves the organization settings, and brings in the deployment settings to the same view with a shared sidebar for navigation.