How to squash work-in-progress migrations
Would it be better to have only one migration in place of a few WIP ones you created when working on a feature, that have silly mistakes and correct or cancel out each other? It would, and it is possible.
Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!
Would it be better to have only one migration in place of a few WIP ones you created when working on a feature, that have silly mistakes and correct or cancel out each other? It would, and it is possible.
Post a comment