Skip to content

chore: add setting to enable multi-organization ui #13266

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

Merged
merged 2 commits into from
May 13, 2024
Merged

Conversation

aslilac
Copy link
Member

@aslilac aslilac commented May 13, 2024

The frontend code is absolutely plastered with code that assumes there is only one organization, and that you're only ever active in the default organization. As we begin working on the frontend bits of multi-org support, obviously that needs to change, but it is likely to result in breakages along the way. @Emyrk and I are fine dealing with those, but it'd be best to spare the rest of you. 😄

(The plan is to remove this once we've made some progress, and feel that it is stable enough)

@aslilac aslilac requested a review from Emyrk May 13, 2024 18:54
Copy link
Member

@Emyrk Emyrk left a comment

Choose a reason for hiding this comment

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

👍 Let's commence chaos progress!

@aslilac aslilac changed the title chore: add setting to enabled multi-organization ui chore: add setting to enable multi-organization ui May 13, 2024
@aslilac aslilac merged commit 2b29559 into main May 13, 2024
28 of 31 checks passed
@aslilac aslilac deleted the multi-org-ui-setting branch May 13, 2024 20:41
@github-actions github-actions bot locked and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants