Replay migrations for multiple branches workflow #10767
fgirardey
started this conversation in
Feature Requests
Replies: 2 comments 2 replies
-
Also facing the same problem. @fgirardey did you find a graceful way yet? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Thanks mate
…On Sat, 13 May 2023, 08:21 Florian Girardey, ***@***.***> wrote:
Yes I found a workaround, I commit the migrations.json file in the main
trunk and run the npx nx migrate --run-migrations command in each branch.
I think that the Nx documentation has really improved since my question :
https://nx.dev/recipes/other/advanced-update
—
Reply to this email directly, view it on GitHub
<#10767 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6UHS7FH2BYFDFAPAXL76TXF4SAJANCNFSM5Y6A4NNA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi folks!
I have a problem with Nx migrations when we work on multiple branches, some of us add libs or Nx plugins in our branches, and we want to migrate from Nx 13 to Nx 14.
The problem is that if we update the workspace on the common trunk, the migration process will obviously miss the new libs that are coming from our branches.
Maybe if we could manually trigger previous Nx workspace migrations we could repeat the migration process in our branches to not miss anything.
For now the only solution we found is to migrate Nx on all branches and then handle the merge conflicts in each branches, which is not ideal.
Maybe there is a problem with the way we work with Nx, I don't know, how do you guys deal with migrations and multiple branches?
Beta Was this translation helpful? Give feedback.
All reactions