From 3b5c4ad36c8bd3e65a6e8247ab6ecc8a41b571a9 Mon Sep 17 00:00:00 2001 From: Andrei Kaleshka Date: Fri, 19 Jan 2024 23:32:43 +0100 Subject: [PATCH] Update README.md (#42) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4671033..d9e22dd 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Does switching between branches in your Rails app mess up the DB schema? -Keep the DB schema actual across branches in your Rails project. Just install `actual_db_schema` gem and run `db:migrate` in branches as usual. It automatically rolls back the *phantom migrations* (non-relevant to the current branch). No additional steps are needed. +Keep the DB schema actual across branches in your Rails project. Just install `actual_db_schema` gem and run `db:migrate` in branches as usual. It automatically rolls back the *phantom migrations* (non-relevant to the current branch). No additional steps are needed. It works with both `schema.rb` and `structure.sql`. ## Why ActualDbSchema