Takeaway from the Phantom Migrations lightning talk: instead of manually dropping/reseeding the database when switching between branches with incompatible migrations, use a gem that records executed migrations in the temp folder and uses that history to roll back migrations that no longer exist on the target branch (assuming they are reversible). Then `rails db:migrate` brings the DB back in sync.