You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say you have two people working on an app, both in a separate branch. (branch-a and branch-b) First the person on branch-b creates a migration to develop their feature, then the person on branch-a.
Now branch-a gets merged and the migration from that branch ran in production. Sometime later branch-b is merged, but the issue is that the branch-b migration doesn't run production, I assume because it's "older" than the last one that was ran from branch-a.
Any ideas how to fix this?
The text was updated successfully, but these errors were encountered:
For that reason and others I proposed #21 which got merged and you just need to make sure you use the latest npm version, then execute migrations with -i and it will apply all migrations regardless of their timestamp.
Say you have two people working on an app, both in a separate branch. (
branch-a
andbranch-b
) First the person onbranch-b
creates a migration to develop their feature, then the person onbranch-a
.Now
branch-a
gets merged and the migration from that branch ran in production. Sometime laterbranch-b
is merged, but the issue is that thebranch-b
migration doesn't run production, I assume because it's "older" than the last one that was ran frombranch-a
.Any ideas how to fix this?
The text was updated successfully, but these errors were encountered: