Friday, February 1, 2019

Rollback to a reasonable Entity Framework 6 migration when you change branches to start a new story?

This could be a smart move. If you don't do this you are apt to make a migration in your new story that trys to drop a column that won't exist in other environments or some other tangled gobbledegook of horror. Just fall back to before the things you just did in the story you stepped away from. If you can merge to dev right away you can just branch the new story from dev to get around this pain point, but if you have to wait on a pull request...

No comments:

Post a Comment