Repository navigation
make the dev user's organizations insiders on every dev sign-in - #221
Merged
Merged
Conversation
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.
Dev sign-in (
POST /auth/dev/login) now marks every organization the dev user owns as an insider, every time it signs in, so organizations made after the first sign-in become insiders too. In development the dev user always gets every experiment and can pick each persona's model, with no trip to the internal admin. Throwaway users ({fresh: true}, used by the screen map's crawl) are left alone. The newmarkOwnedOrganizationsInsiderin@proxy/db/organizationsets the flag, and the route is only reachable when NODE_ENV is development.Open workspace in Conductor