[Feature Request] Rollback intelligence for migrations

[bkuhl]

Rolling back is a complicated process and it'd be sweeeeet if this package handled when to run database rollbacks. It'd require looking at the current/target releases to figure out how many/which migrations needed to be rolled back. This might be able to be accomplished by looking at the output of a diff between the releases? If it required a database connection, a Laravel package might be in order.

[philbates35]

+1 This would be an excellent feature.

[ikari7789]

Sorry for the late response. I'll be helping maintain this plugin for the foreseeable future.

I also agree that this would be an excellent feature, though as you said, it is quite a complicated process. If you can think of any good way to handle this I'm all ears. I haven't even made migrations by default as part of a release as some migrations may require special timing in how they are executed (i.e. need to take the site down while running if some columns changed or something).