Open kevingates opened 3 years ago
@kevingates Generally speaking, don't remove the code for a migration without first removing the migration. That being said, as long as you're not rewriting history in the git repo, then you can always go back to the commit that contains the migration code and roll back the migration from there.
Thank you for your clarification. Is there a chance that we could get a direct article on the official docs for the standard process for this? There is not a lot of articles on the proper rollback strategies, even unofficial articles outside the Microsoft docs.
I understand you can make migrations with Entity Framework (Core). However, what isn't clear is what happens if someone reverts in GitHub the changes.
So here is scenario 1:
Now what?
So here is scenario 2:
Now what?
Summary
It's not clear what happens in term of Database EF Migrations when you have Git Reverts.
An article describing the suggested methodology would be incredibly helpful.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.