-
Notifications
You must be signed in to change notification settings - Fork 186
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
feat(regions): move project branches and commits #3843
feat(regions): move project branches and commits #3843
Conversation
…t-branches-and-commits
…t-branches-and-commits
📸 Preview service has generated an image. |
.onConflict(Workspaces.withoutTablePrefix.col.id) | ||
.merge(Workspaces.withoutTablePrefix.cols as (keyof Workspace)[]) | ||
|
||
return workspaceId |
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.
we should check how workspaces are propagated to the region db and use that to publish the change:
- always update the main db
- update (fake) the main db and use the publish system to update the region
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.
It appears that we quite literally only care that the workspace id is defined in the regional database for foreign key constraints. Anything user-visible is pulled from the main db record. Simplified this to a copy then ignore on conflict.
📸 Preview service has generated an image. |
Description & motivation
Changes:
region2
to CI and local test dependencies (so we can test moves between regions, instead of main => region)hooks.ts