Bug: Autogenerating and running migrations tries to generate schema_migration model twice

@jay1 very helpfully provided us with some detailed specifics over email (thank you so much!), and so far it seems like one way this can fail is if:

  • You fork an environment, like from primary to staging
  • In staging, you delete an existing model, like post, and then re-create the model again with different fields, but keep the same name post
  • The migration script then (erroneously) tries to create a model of post when run, causing failures both in the model and menu item creation

I’ve reported this issue to the devs and will update here as soon as we get more info!

@ldc Could that also be what you experienced, or do you think it was a different issue?